I was doing analysis for a new feature we have ticketed in Jira yesterday and thought, “Wow, I sure could use the advice of a designer.” So I texted @gschmidt, and we had a brief discussion, and it was very helpful.
Perhaps we should have a process for sending Jira tickets for UX design that doesn’t rely on who the devs may have met at the Implementer’s Conference?
I defer to @c.antwi, Greg, and any other designers here, but my starting-point of an idea would be that
there should be a status on Jira “needs design”
devs should send tickets to that status as appropriate
OpenMRS should have a set of designers that monitor and work on the tickets in that status
I think I recall someone at some point suggesting that there be a designer equivalent to the “dev-n” designations? Perhaps that could tie into this really nicely?
Oh nice, yes, so that could be the Jira support for what I’m talking about. But the core of what I’m proposing is that there be a team of designers who can be called on for design help, and/or will keep an eye on that “Design” status in Jira. Some process around this could really help make design a more integral part of OpenMRS development.
Wondering if using this spreadsheet (or something like it) could help identify those who might want to be a part of such a group or contribute their design skills to a particular Jira ticket or project?
Btw ‘needs design’ might mean ‘needs architecture/code design’, so we need to either distinguish here or make sure that a single Jira status can encompass a broader set of possibilities when it comes to design.