Is there a way to see how long certain tickets sat with different assignees?

[Mark Geris]

We want to improve our processes to have a report that can tell us how long different tickets sat with different assignees in JIRA. 

The hope is to be able to identify different teams and individuals which take longer to move or resolve the issues in order to coach those people to help speed up our overall throughput of issues.

Thank you

[Bloompeak Support]

Hi @Mark Geris

Welcome to the Atlassian Community!

You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Time in Assignee report. For further details, please check Status Time Reports How to Videos.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. 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.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @Mark Geris 

Building a custom automation will most likely be hard to build and maintain. So it will be expensive. I suggest you use a marketplace app for that.

Our team at OBSS built Time in Status exactly for this. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. 

   

The app also has Status/Assignee Composite Reports that can show assignee times broken down to statuses or vice versa.

 

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend. 

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. It supports both Company-Managed and Team-Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

   

https://marketplace.atlassian.com/apps/1211756/

EmreT

[Craig Nodwell]

Hi @Mark Geris welcome to the community.  There are some jql queries that would give you some information on when the assignee changed but I don't think this would satisfy your requirements.  I'm sure there's addons that would assist. 
One thing you could try is implementing mandatory Work Log entries when changing assignees... or workflow transitions. 
Another possibility is that this could be scripted out if you have a tool like scriptrunner in your Jira instance.