I am trying to generate a way for us to track the time from when a bug is assigned to a team to when it is completed.
When *some* bugs are created there is no scrum team assigned because we do not know who will take responsibility. QA has a meeting where they delegate these bugs to the appropriate teams.
We are encountering an issue where some bugs get forgotten about and we want to be able to track the time a bug is assigned to a team to when it gets actioned on.
Additional information:
- We have one project with boards for each of our 7 teams
- Each team is categorized by a custom field "Scrum Team" and the teams are A, B, C, etc.
- We already track the time when a bug is created to when it is closed. However, some bugs take some time to be assigned.
Hello @jnijjar
You can also try Time in Status for Jira Cloud developed by my team.
It generates 7 types of status reports including a Time in status and Assignee time reports.
Time in Status report shows how long an issue has been staying in each status.
Assignee time report shows how long each assignee has been assigned to the issue and how long it takes to solve each of them.
Hope you find it helpful.
Regards, Mariana
Hi @jnijjar ,
Not out of the box. This is something you can do similarly in Jira Service Management as part of its SLA feature.
Here's a suggested add-on that may help you what you need:
https://marketplace.atlassian.com/apps/1211843/time-to-sla?hosting=cloud&tab=overview
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @jnijjar ,
As an alternative, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count. The reports are based on history of issues and you can trim the history range.
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). And all these are available as gadgets on the dashboard too.
Here is the online demo link, you can see it in action and try.
If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, does Time to SLA work with non-JSM projects too? Cool?
Another popular add-on for this is Time in Status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Darryl Lee - Yep. It works for non-JSM projects too. :)
Time in Status is another great suggestion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@jnijjar ,
As the builders of Timepiece - Time in Status for Jira app mentioned above, I would like to make some contributions. There are multiple ways Timepiece can help you.
You can use the Status Duration report of the app, which will effectively give you the time each issue spent on each status.
Alternatively, you can use the Assignee Duration report, which will give you the time each issue spent assigned to each assignee.
You can use the Group Duration report, which will show you the total time each issue spent assigned to members of each user group. (This one works like Assignee Duration report but instead of reporting each assignee as a separate column, it combines them into user group columns.)
Additionally, you can use the super-advanced and super cool Any Field Duration report to see how much time each issue spent with each "Scrum Team" field value. This report will let you see the time before and after a Scrum Team was assigned to the issue.
Even better, once again using the Any Field Duration report, you can combine the Status Duration and Any Field Duration options above (by choosing both Status and "Scrum Team" fields for this report) and prepare a report that shows how much time each issue spent on each status with each Scrum Team field value. It is not easy to explain verbally but I am sure it will be perfect for your case.
You can also get averages of these values, grouped by fields you select. For example, see the average In Progress time for each Scrum Team.
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.
Using Time in Status you can:
Timepiece - Time in Status for Jira
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.