I am wanting to get some view on the 'Time in status' report.

[Kara-Lucia]

Currently this is in the Feature Requests space, I did not know that this was a thing and am stoked to have more visibility over improvement areas.  However, because I did not know this function of Atlassian existed maybe you didnt either.

Here is a link to the feature, they have many others, where you can raise more awareness over issues.

https://jira.atlassian.com/browse/JRACLOUD-60841

[Bill Sheboy]

Hi @Kara-Lucia 

Are you asking a question about time in status, or just providing visibility to the suggested feature?

There is already an out-of-the-box JIRA, dashboard gadget to show average number of times in status, and I find it unhelpful for what it can show.

There are marketplace add-ons you can buy to show time in status.  No doubt, others will respond to your post to suggest *their* products.  :^)

Or you could build your own, using the REST API, log extraction with webhooks, or the built-in automation rules and custom fields.  (Our teams did the last one, and got lots of great information.)

Best regards,

Bill

[Kara-Lucia]

Hi Bill thanks for the reply..........my intention was to provide visibility to the suggested feature in the hopes people would vote.

But, I am interested to know more about how you built your own - is this an easy process??

Regards,

Kara-Lucia

[Bill Sheboy]

Hi Kara-Lucia,

Sort of... Once we learned about automation rules and had a good understanding of our workflow, it was easier.  What we built can be re-used by any team in our instance.  It took us a few days to figure out the automation quirks, implement, test, and deploy.

Here is a summary of the steps:

• Confirm the team wants to measure and will take action with the data.  If not, stop and don't proceed.
• Work with the team to match their workflow to JIRA status values and column on a board
• Identify what you want to measure, such as specific cycle times, lead time, WIP, age of WIP, etc.
• Identify the relevant status values impacted by each measure
• Add custom fields to record the start and end date/time for each measure
• Add custom number fields to display the measures
• Add automation rules
  • Add rules to record the start and end date times for status transitions
  • Add rules to compute the measures when issues are resolved
  • Add rules to handle edge cases: cloning, abandoning, and re-opening closed items
• Test!  I recommend creating a test project to implement the rules using test stories.  Once done, your site admin can easily copy the rules to a specific project for use.

Two big advantages of this approach over buying an add-on: the result matches how you actually work, and measures are saved with issues.  (The add-ons appear to recompute these values from logs each time you want to look at them.)

You can learn more about the automation rules here:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

Best regards,

Bill

[Mehmet A _Bloompeak_]

Hi @Kara-Lucia ,

You can use Status Time app.

If you are looking for a free solution, you can try Status Time Free.

[Emre Toptancı _OBSS_]

Hello @Kara-Lucia ,

I wouldn't want to let @Bill Sheboy down so here I am recommending our app for this need :P

Our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average InProgress time per project and per issuetype). You can also combine statuses into consolidated columns to see metrics like Cycle Time or Lead Time.

The app has some advantages over building your own solution:

• It is a "ready-built" solution that provides various types of reports so you don't have to work for building, testing and later maintaining your solution. Let's be honest, building a custom solution for this with automation, testing it, rolling out to other teams and maintaining it is serious work.
• The app calculates its reports using already existing Jira issue histories so when you install the app, you can get reports on your past issues as well.
• The app has custom calendar support, which would not be possible to have with automation. (Details below)
• The app draws various charts to visualize the data.

Custom calendar support means you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
• Export your data as XLS, XLSX or CSV.
• Access data via REST API.
• Use one of various chart types.

Timepiece - Time in Status for Jira

EmreT