Filtering historic resolution dates

[Marta Grzegorzewska]

Hello fellow Jirers,

I encoutered a problem when trying to drill down the historic data for my team. The outcome I wanted to achieve:

• get the numer of resolved tickets per month
• the tickets resolved should be set to "resolved" while being assigned to the specific assignee group member
• there is no limitation to specific project, as the assignee group is assigned to different projects and they action upon tickets from different teams and projects

So far I have tried the below query:

assignee in (membersOf(dab.admin.web)) OR "Grupa obsługująca" = dab.admin.web OR assignee in (membersOf(dab.admin.backend)) OR "Grupa obsługująca" = dab.admin.backend and status = Resolved and resolutiondate >= "2019-06-01 00:00" and resolutionDate <= "2019-07-01 00:00" ORDER BY priority ASC

However, setting the above query does not filter the list of all tickets.

I would appreciate some help showing me where should I introduce some changes to the query,

Cheers,

Marta

[Roman Kersky · Accepted solution]

HI. you need add "("   and ")" . I marked it by bold font

(assignee in (membersOf(dab.admin.web)) OR "Grupa obsługująca" = dab.admin.web OR assignee in (membersOf(dab.admin.backend)) OR "Grupa obsługująca" = dab.admin.backend ) and status = Resolved and resolutiondate >= "2019-06-01 00:00" and resolutionDate <= "2019-07-01 00:00" ORDER BY priority ASC

[Marta Grzegorzewska]

Thank you so much @Roman Kersky , indeed, simple correction and worked for me. Cheers!

[Olga Videc · Accepted solution]

Hello @Marta Grzegorzewska 

This should do the trick

resolved >= 2019-06-01 AND resolved <= 2019-07-01 and resolution != Unresolved and (assignee in (membersOf("Architect")) or assignee in (membersOf("Engineers")))

You can add a gadget to your dashboard, I would recommend the pie chart for monthly 

and you can see a number of issues per agent/monthly

OR if you want to display multiple months you can use Time since gadget and display number of the issue resolved per month, but don't forget to edit the time in the filter to display multiple months.

BR, Olga

[Marta Grzegorzewska]

Thank you @Olga Videc , it worked for me! I think the critical part was to add also resolution != Unresolved, thanks for the suggestion.

Also, good suggestion on the pie chart, will to play with it.

On the other hand - is there any possibility in Jira within dashboards to show concurrents months data on a bar chart? If I am having different parameters for months in every query and every search done separately, I believe this is not possible to have all the data in one chart, but maybe there is some Jira trick I am not aware of?

Thanks again for your exhaustive help.

Cheers,

Marta

[George Mihailoff]

@Marta Grzegorzewska sometimes your project workflow doesn't have a proper resolution configuration that leads to an empty resolutiondate field and not working search.

First, you need to configure resolution setting -- https://confluence.atlassian.com/jirakb/jira-issues-need-a-resolution-826873869.html

For the historical data, you can try our free addon (Quantify). Because we deal with things like time in status, throughput (resolved tickets per period of time 😉 ) and other Kanban metrics we have the data to fix resolution dates. We recently released a special tool for this -- resolution checker.