So we have a Metrics in place in our project to showcase the defect ageing where we track the difference between the Created Date and the Closed Date. However, since there is no field for Close Date, we have to check every closed issue and manually note down the Closed Dates. It would be great if we could somehow directly access the Closed Dates instead of finding out from the history of the issues.
You can use Status Time add-on. It displays the status entrance date of issues in bulk.
If you are looking for a free solution, you can try Status Time Free.
Also, you can try the free trial version of solution Time Between Statuses (cloud & server) which will help you automatically get time from one status to others. Moreover, you will be able to set statuses to pause the timer.
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.
Is there a reason you're not using resolved date?
When an issue moved to a "done" status - you can set a resolution against the issue. For example, you could:
^ You can then compare created date to resolved date.
If you're using Next-Gen, resolved date is set when an issue reaches the last column.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ste Wright,
I hope you're safe and doing well.
The picture at the bottom may help in better understanding the bug workflow in my project.
It might happen that the developer who is working on the issue has resolved the bug in a lower environment but is yet to deploy the code to the exact environment where it was reported. In that case, the bug is marked as 'Resolved' with an appropriate resolution (as you mentioned). But it is not 'Closed'. The bug gets 'Closed' only when it passes the retest in the exact environment. Therefore, the Resolved Date may not reflect the precise day when the bug reached its end state. To calculate the defect ageing, what I need is to find the date when the bug reached the end state, i.e., got 'Closed'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Choose one of your statuses to be set via Resolved Date. In this instance, I'd use resolutions for Closed - it's the absolute date of completion rather than Resolved. Retest is after Resolved where work is technically continuing.
You could use Automation for the second field. Below I've used Resolved to be set by another field - but this works for either status.
You'll need to be a Jira Admin to create the field. Then...
^ Remember, if you add the field to a screen it would be editable by users. I would create it and then keep it hidden from screens - making it harder for a user to modify.
Next you need to create an automation rule. You need to either be a Project Admin for a project-specific rule - or a Jira Admin for a global rule.
As a Project Admin...
^ Now each time an issue is transitioned to resolve, this field will update with the current date or date/time, depending on which type of field you chose to create.
You can access global rules from the project screen - just press the "Global administration" hyperlink. Or you can get to them via settings - go to Settings > System > Automation Rules
With this you could compare Resolved Date, Fix Date and Created Date :)
Ste
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.