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.
Time/Days in Status is a very common request so I spent a little time ironing out a reasonably simple solution. It does require an add-on, but it's the free version of Automation for Jira. This best suits Jira Server, but does work on Cloud as well. Just be aware that the free of version of the cloud add-on has a monthly limit on rule executions.
@Jonathon S - this was so easy to follow and worked like a charm!! thank you so so much for putting this together. The only thing that could have made this easier would have been if you including instructions on how to find the customfield id (or a link to a site/thread with instructions) - other than that, this was great and I think will be very useful for the people on this thread.
Hey Jonathan - I'm wondering if you have any advice for where I may have botched the setup here, as I'm not seeing the correct days in status on my cards or in my search. It either shows me an issue has been in the status for "1" day or for "18,211" days- and neither are correct haha.
Any ideas on where I could/should troubleshoot this?
Hello all, apologies for the delay - the access issue has been resolved :)
For those experiencing issues with the calculated date, it might be helpful if you post the smart value function you've written (shown in step 4.3)
Feel free to comment on the actual page itself as that might allow me to more quickly respond.
apologies! should be all good now.
Please note: For those unaware, Atlassian purchased Automation for Jira and has begun offering the automation rules described in my how-to guide as an out-of-the-box cloud feature. I have not verified which version or tier this applies to but, as far as I know, the tool itself will still function as described in my guide (just some of us won't need to install the add-on anymore). I will update the page soon once I've dug a little deeper into this!
Hi @Jonathon S
what if I want to have hours in the status "in Progress", not days. I mean I have updated the rule "Days in status" where I have updated the JQL query in the "Schedule". But how can I make this work with hours? It is not totally clear to me.
Thanks in advance and for the great guidance.
Hi everyone, glad this has helped some people!
However, please note: at this point, this guide is likely out-of-date for some people.
Due to (how quickly) changes to automation for jira and cloud in general have been rolled out, I am no longer confident these steps will accomplish exactly what it was initially created to do. I will try to update it soon!
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.
There are no built-in solutions for cloud version now.
But this problem can be solved by using an app from Atlassian Marketplace, like Time in status for Jira Cloud by SaaSJet created by my team.
Try its free trial version and appreciate all of its benefits for your project management process.
Can I use Time in Status with JQL filters to show the average amount of time a group of issues spent in a given status?
For example, based on a filter of 100 issues, what was the average time those issues were 'in progress'? Additionally, are there any ways I could visualize this data such as in a Jira Gadget?
Thanks and please let me know,
With all due respect, your plugin does not resolve this issue in the Cloud version. Having tried it, it does not cleanly report (nor allow for export) the data from a project's workflow of the Cycle Time (which in effect "Time in Status" is) for each activity state.
Sadly, my trial has expired, and I can't go back and scrounge around for this.
While my trial was active, I did correspond with someone from your company about this, and had left the door open where I would take time from my schedule to walk them through where my concerns lay....I received no response desiring clarification on my part.
Yes you can use Time in Status by OBSS to get average durations for issues in a JQL filter. Both server and cloud versions support this.
Considering the fact that average calculation has to go through not all issues but also all issue histories, it can be expensive for your Jira instance if you have a large number of issues. Currently, due to performance considerations, average calculations are intentionally made available only through file exports and REST API. We are working on possible optimizations for average calculations and plan to make this available through Jira UI in future versions.
We are glad to get in contact with you here. Our support team tried to reach you at the beginning of May but could not get a response.
As we said in our response, both Server and Cloud versions of Time in Status allow export of report data in XLS, XLSX and CSV format. The export button is on the far right of the toolbar on the report screen.
We technically can't give you another trial for cloud but we will be happy to extend your trial if you have a Jira Server. You can also see the live demo by going to plugindemo.obss.com.tr
For any questions or feedback, you can reach our support team by sending an e-mail to firstname.lastname@example.org .
@Marcelo Lopez It looks like you wrote about another plugin. Our application is "Time in status for Jira Cloud" by SaaSJet.
We discussed the export and time format with you. You have sent us a few interesting ideas.
Contact us via email@example.com if your trial period have expired, and we will provide you possibility to continue using the app so you can appreciate all of its benefits:
- Functional for 7 types of reports generation: Time in Status, Assignee Time, Average Time, Status Entrance Date, Time in Status per Date, Status Count and Transition Count.
- Possibility wiev data as tables and as charts
- Data export
Now you can get the average time in status using our app Time in status for Jira Cloud by SaaSjet.
In the updated version of this add-on you can measure your team delivery with new kinds of reports and also view them as charts (Pie, Bar and Area Charts).
You can try all of the above and much more with the free trial.
Let me know if this is helpful.
You may want to try out the plugin, Agile Tools : Epic Tree & Time in Status
It provides 3 major functionalities in one add-on
We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events