Automation to control time in eache status

[Eduardo Bentes Carneiro]

I want to make a automation to tell me how many minutes my team spent in ench status.

It will basically work like:

When issue is transitioned of one status for another one then tell me the time spent in that status

Any ideas

[Valeriia_Havrylenko_SaaSJet · Accepted solution]

Hi @Ashley Byrd 👋

If you consider installing third-party add-ons, option for you can be Time In Status. You can get time spent in that status when issue is transitioned of one status for another one. Іdentify the loops in the workflow in a few clicks.

Add-on developed by my team.

I hope you find this helpful 🚀

[SilkeS]

Hi @Valeriia_Havrylenko_SaaSJet ,

Thank you for your contribution. I removed a promotion that’s against our  Atlassian Partners - Rules of Engagement . Please take a moment to review our guidelines so you're aware for next time. Thanks!

[Ayça Erdem_OBSS_ · Accepted solution]

Hello @Eduardo Bentes Carneiro 

You can achieve this with Jira Automation, but setting it up to measure time spent in each status would require complex configurations, development, testing, and ongoing maintenance making it quite costly. Using an app is a much more efficient and cost-effective solution since the necessary data is already available in the issue history.

I recommend Timepiece- Time in Status developed by my team at OBSS for Jira, which mainly allows you to see how much time each issue spent on each status or each assignee. 

Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend. 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Timepiece reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts. And the app has a REST API so you can get the reports from Jira UI or via REST. Also you can export the reports in to various formats easily. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process.

Hope it helps,

Ayça 

[Sebastian Krzewiński · Accepted solution]

Hi @Eduardo Bentes Carneiro 

But why? :D I have many examples how this idea didn't work for any report.

Answering your question: You will need 2 field (one for moment when ticket enter status and another one for when leave status). Then you can make a calculation with smart values (https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference---). Rule can work like below:

- triggered by status change

- set leave status field

- make calculation

- set enter status field for new status

Regards,

Seba

[Danut M _StonikByte_ · Accepted solution]

Hi @Eduardo Bentes Carneiro,

I'm not sure if it's possible to do this for each workflow status via automation, because this would require a lot of custom fields and complicated calculations... And what if an issue has gone through a status multiple times?!

A much easier solution would be to use a plugin from Atlassian Marketplace that is capable to make this type of calculations.

In case you want to try a plugin, our Great Gadgets app offers a Time in Status gadget that can calculate and display this for you with just a few clicks. 

Beside the chart, it can display a Data tab with a report showing the time spent by each issue in every status, which you can easily export in CSV.

Danut

[Mehmet A _Bloompeak_]

Hi @Eduardo Bentes Carneiro ,

You need to apply the below steps for each status you want to track. Below is an example for "In Progress" status.

• Create a custom field named In Progress Start Time Choose the Date Time Picker field type. Our automation will use this field to store the time when the issue is transitioned to "In Progress" status.
• In the first automation:
  
  • Rule name: Store time issue enters In Progress status
  • Rule trigger: Issue transitioned
    • From status: leave blank
    • To status: In Progress
      
  • Rule action: Edit issue
    • Choose fields to set: In Progress Start Time
    • Field value: {{now}}

• Create Number type custom field named "In Progress Duration"
• In the second automation:
  
  • Rule name: Calculate and Store time spent in In Progress status
    
  • Rule trigger: Issue transitioned
    • From status: In Progress
      
    • To status: leave blank
  • Rule action: Create variable
    • Variable name: NumberOfSeconds
    • Smart value: {{now.diff(In Progress Start Time).minutes}}m
  • Rule action: Edit issue
    • Choose fields to set: In Progress Duration
    • Field value: {{now.diff(In Progress Start Time).minutes}}

As you might guess, it will be hard to maintain custom fields and automation rules for each status. As an alternative, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app.

For further details, you can have a look at Status Time Reports How to Videos.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

If you have any questions, feel free to schedule a call with us.

Hope it helps.