I need a field which populates time elapsed in current status. Currently I have placed the script in post-function on transition but it updates only on transition, but it can't tell the current duration in the current status, any pointers will be helpful.
For Jira Cloud, you can use Status Time add-on. It generates status time report based on your working calendar.
If you are looking for a free add-on, you can try the free version, Status Time Free.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jagan Shankar and @Joe Pitt
Time in Status for Jira Cloud by SaaSJet could be a great solution for you.
This app can generate reports of how long your issues stayed in a specific status. It provides the possibility to view data as number tables or as charts and export them as XLSX or CSV files.
Also, using this add-on you can get graphical and numerical data at the single issue view tab.
Hope it helps to resolve your question
Best Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may be able to do it with a listener that fires the script. I haven't used them and don't know if the event listener will fire if someone just views the issue. Is says 'whenever anything happens to an issue' but just viewing it may not count
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply.
But something I need which will update by itself even when there is no action on that ticket.
Lets say, i have moved the ticket to Assigned status now, so it is 0minutes in this status. if I do a query after 5minutes, will this ticket will show up that field with value as 5 minutes ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nothing in JIRA will allow that. I would look for a plugin, but being the cloud limits what plugins you can install. You would need a continuous clock running in the background for EVERY issue. That would be a big drain on the system resources.
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.