For those who are interested, our team at OBSS developed Time in Status for this exact need. It is available for Jira Server, Jira Data Center and Jira Cloud on Atlassian Marketplace.

https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud

• The app reports on how much time each issue spent in each status, each assignee or each group.
• Can show durations as days, hours, minutes or seconds.
• Can report based on a 24/7 calendar or custom business calendars you define.
• Can also report the number of times each status and each transition was used.
• Can calculate average durations or counts, grouped by the fields you select.
• Can export report data as CSV, XLS or XLSX.

Emre TOPTANCI [OBSS]

I can see that this suggestion is for the JIRA Server. I wouls, however, love to see it happen for the JIRA-DC.

REgards,
Rahul Savaikar

Logging a vote for this feature. This request is closest to the core business challenge (the linked ones less so but related).

The business challenge is to see total time an issue spends in a particular status. Not only to report on it, which is covered by the Time in Status plugin, but to see it in the Issue Navigator and constrain results returned using JQL. For example, I may want to see issues that have spent more than 7 days in the "In Progress" status, which indicates they may be getting stale (beyond just Updated Date). Or maybe I want to build aging queries that show issues that have been On Hold for 0-30 days, 30-60 days, etc with different filters by assignee, to create an intelligent support team issue filter widget.

Building this feature would be tricky, since JIRA would have to make a data column available in the Issue Navigator dynamically that aligns with all statuses in an instance. Such as "Time in [status]". Almost like a checkbox on the workflow editor for each status, if you want to include the workflow statuses in the column selector. And I don't know how you'd handle multiple statuses with the same name but different IDs in different workflows in different projects, that too would be tricky.

But the business need to refine JIRA data in queries based on total time in status is much needed. Note: it's not good enough to have a calculated field that runs time between two date fields set to date/time when transition occurs, since it does not account for cycling back through a status. Such as In Progress > Done > In Progress   and adding up the total time spent in In Progress, even though it was not linear.

Thanks for considering this feature!

Please provide this feature.