I am trying to make decisions on class of service from the board or issue view before digging in to the control chart.
So far, I have added a custom 'Time in Status' field called 'StatusDuration' and administered it to display in 2 projects. I believe this is different than the '[CHART] Time in Status' that is referenced in time-in-status.
However, no StatusDuration is visible as part of the issues that I'm looking at. I have enabled the JIRA Charting Plugin mentioned in the thread above which shows "time in source status" as part of a new tab called transitions, but that only aggregates the history and doesn't show how long it's been in the current status.
Even if it's not available in JQL (which would be even better), I understood it to be available as it lets me associate it with screens:
Hello, the "Time in Status" or "[CHART] Time in Status" fields are not editable and therefore will not appear on issue screens. The field just needs to be assigned to the appropriate issue screen(s) and are intended to provide data to the "Average Time in Status" gadget. We've checked this on a test instance and we have been able to get the "Average Time in Status" gadget working . We used "[CHART] Time in Status" in our tests. For more information on the gadget, please see - How to use Average Time in Status gadget. Custom Field type 'Time in Status' is only useful when used together with the JIRA charting plugin.
I'm having the same issue in my instance of JIRA Cloud.
Is anyone from JIRA reading these requests? Hope someone can help. Time in Status is of critical importance to our management strategy.
For tracking issue duration in the Cloud version, you should use an additional plugin. For example, you can try Time in Status for Jira Cloud. It allows generating reports of how long issues have stayed in a specific status.
Also, using the Jira's filter options to select a particular user, this add-on helps to monitor the time that team members are spending on a request. So, you can avoid the waste of time at unproductive delays in your processes.
Hope this helps!
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs