Is it possible to set a time interval for each of every person and monitor between the time interval how many issues the given person has solved and what is the average time of the solved issues?
Any help would be greatly appreciated.
Hello @Csiszer Csongor ,
"How many issues a user resolved?" and "How long it took?" are actually two different questions. Let's approach them one by one.
How many issue a user resolved?
In order to get this report, you need to be sure that a field on the issue holds the name of the user that resolved the issue. If you leave the issues assigned to the user that resolved it, than "assignee" field will serve this purpose. This is not a bulletproof solution but might work for you.
Alternatively, you can also consider creating a single-user-picker custom field named "Resolved By", edit your workflow, modify the "resolve" transition and copy the name of the user that executed that transition to the "Resolved By" field. This way, you can be sure that the "Resolved By" field always contains the name of the user that resolved the issue.
Once you decide which field to use, you can use "Issue Statistics" or "Two dimentional Filter Statistics" gadgets on your dashboard, configure the dashboard to group the data by "Resolved By" field and see how many issues were resolved by each user.
How long it took?
That is another story. Jira keeps CreatedDate and ResolutionDate values on each issue so you can export these to a file to do your own calculations.
Alternatively, if you have Jira Service Desk (or Jira Service Management as it is called now) you can define SLAs to measure that duration.
If you have Jira Software, Control Chart of Kanban Boards might also help you. If offers limited flexibility but will help with general use cases.
For anything further, you will need to do some custom development or user one of the existing marketplace apps.
For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.
Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can also combine statuses into consolidated columns to see metrics like Resolution Time, Ticket Age, Cycle Time or Lead Time. You can calculate averages and sums of those durations and counts grouped by issue fields you select. (For example use the aforementioned ResolvedBy or Assignee fields to see the average times for each user, like below)
The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.
The app has Custom calendar support which means you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)
Finally, the app has History Trim feature. This feature allows you to report on a subsection of issue histories instead of the whole history. Very useful when you want to focus on changes made during sprint or project phase.
Using Time in Status you can:
Hello @Csiszer Csongor
As an alternative solution, you can try Time between Statuses (server version). Besides generating a report on the time between statuses, you can export it as XLSX or CSV file for further analysis.
After exporting the report, you will have the ability to filter data by Assignee and calculate the average time that has been spent on each issue.
I hope it helps.
Best regards, Mariana
Hi @Csiszer Csongor ,
You can achieve this easily using Time to SLA and its dynamic duration feature.
Just define your SLAs as wish. One way to go is starting your SLAs with Jira Field: Created or with the first status of your workflow and ending your SLAs with Jira Filed: Resolved or with your "Resolved" statuses (Done, Closed etc.). Set your SLA Goal as Dynamic Duration and you are done!
The dynamic duration field allows you to set a different SLA goal for each issue so you can set different SLA duration for each of your users. Moreover, Time to SLA has many useful gadgets, custom search functions, and a reporting feature so that you can monitor your user's metrics: elapsed duration, pause duration, SLA start/end/target dates and so much more!
Please let me know if you have further questions.
Please note that I'm one of the members of the Snapbytes team.
Hi @Csiszer Csongor ,
It is not a built-in functionality inside Jira. You need to calculate yourself for each issue after getting the issue data over Jira rest api or you need a plugin to do the same for you.
We developed Status Time app which provides various reports and one of them is average status time per assignee.
Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project).
Here is the online demo link, you can see it in action and try. Hope it helps.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events