It´s cool that you can flag issues to highlight that they are blocked. I would like to track the resolution time on a flag. How do I see when it was created and how long it took to solve it?
Have you looked at Time to resolution gadget available to the dashboard? It doesn’t show you TTR on an individual issue basis but give you a running average. You can create a filter using “flagged =“ and apply to this gadget.
I had to get creative to do something similar. Here's what I did:
I created an automation rule that sets a custom date field, Date 1, to {{now}} when the flag is added to an issue. When the flag is removed, it takes the difference between now and the Date 1 field (I chose to just use business days) and adds it to another custom field, Number 1. The formula used is {{issue.Number 1}} + {{now.diff(issue.Date 1).businessDays}}. If the issue is flagged again and that flag removed, the Number 1 field will keep a cumulative total of days flagged for the issue. If you didn't want to keep a cumulative total and only the duration of the last flagged time, the formula could be changed to: {{now.diff(issue.Date 1).businessDays}}.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is awesome....Thank you Sir
Sadly, you would think that something THIS OBVIOUS would actually make it into the work to make Jira itself more useful.
But....no.
We need more "broken" roadmaps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@christopher_douglas thanks so much for this, I am getting a negative number for the number of days blocked. Any idea why this might be?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a good solution @christopher_douglas, but it only solves to calculate the time flagged overall, which is useful, but provides partial information, since the flag feature can happen on any status, you loose that information. Following this approach to identify the time flag on every status, then it will imply to create a custom field per status, which I don't like it too much. Another alternative would be to create a new custom field Days in Flag using a similar syntax as in Days in Status field (available in Jira Cloud for Excel/Google Spreadsheet add-ins). Check this question: Jira Cloud for Google Sheets Add-ons Days in Status field pattern and returned value for duration. Then this information can be extracted and used. It can be populated/updated using Jira Automation, it would be something complex to parse using regular expressions, but it at the end it is doable. Then you can use this information for your reports in Excel (via Jira Add-ins). For example to estimate duration on a given status discounting the time the issue was flagged on a given status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Svenja Speen
This is a unanswered duplicate question
It's not trivial to calculate the time till resolved on a issue which was once a impediment (flag)
My suggestion to you is to move the flagged issues to a status in workflow like "Blocked" etc and then either you can use Control chart in Jira to see the lead time. Or you can create a scripted field (from Script runner) plugin which calculates the time duration from when the issue was flagged upto the time it got resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That will work, but blocked isn't a status in a workflow. There is value in seeing which actual status the work item is in when its blocked.
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.