Good afternoon -
I have a query question, perhaps one of fine folks could assist.
We use Jira as an organization to track all issues, across the board. After a couple of months using it, I would like to generate a list of common issues by client.
For example, let's say that Client A had a file that failed within our Application, this happened 4 times over the past month and an issue was opened up for each occurence.
What I would like is to be able to list those issues quantitatively.
So, the query would return the following:
Client A - Bad File - 4
Where "Client A" represents the client, "Failed File" represents the issue type, and "4" represents the number of tickets opened under that issue type.
I know there should be a simple Jira-SQL answer to this but I am not familiar enough with the format of their language to intuit what I need to do.
There isn't really a "count" function, but
It does depend on how exactly you are trapping the information (exactly what data is going into what field), but it sounds like you could do this in either simple or advanced (JQL) filters. You filter for "issuetype = bad-file and client = A and created > -1m" (that assumes client is select list of some sort, but you could be using reporter, component, etc).
You can then display information on filter summaries on your dashboard with "filter statistics". In fact, it might be more useful to drop the "client" clause in this case, and then you can tell the filter statistics to summarise by "client" and it will tell you things like "client A had 4 issues, client B had 6 and client C had 1"
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs