Issue search
Hi everyone, today I’d like to show you something you might have missed when using Relations. I hope so at least, because it would mean that we achieved one of our goals. I’m talking about the user interface of the add-on.
During the design and development of the add-on, we’ve gone out of our way to make Relations look and feel as close to JIRA as we could. We’ve dissected the Atlassian design guidelines, the Atlassian front-end library and the latest version of JIRA to find out exactly how we could do this.
In many cases, this meant using the front-end library provided by Atlassian. But even this library has a limit, not everything is included. Who would, for example, want to include the filters in the basic issue search?
Well.. we do. In the first version of Relations, our users could view all issues linked to a company and query over them using JQL (the query language used to search for issues in JIRA). While JQL is a great language for this, we wanted Relations to be user friendly for anyone. Why would you manage your relations in a tool that some of your colleagues can’t use?
This is why we’ve decided to replicate some UI elements, such as the basic issue search. The decision wasn’t easy. First of all, it costs a lot of time and effort to replicate a UI into detail. Any small difference will be noticed immediately. Secondly, if Atlassian decides to redesign this part of the UI, we’ll have to follow them. And as Atlassian is always improving its products, this happens quite a lot.
So why did we do it then? Easy, for our users. By staying close to the JIRA UI, our users will immediately recognise the UI and know what they can do. There’s no need to learn new UI elements and conventions.
Want to see what it looks like?
Log in or sign up for Devpost to join the conversation.