current time spent in the ON PROGRESS status

[Nico]

i want to track the time when the ticket is transistion to ON PROGRESS , 
currently my refference is this : 

https://community.atlassian.com/t5/Jira-questions/Log-time-to-quot-Time-Tracking-quot-field-with-automation/qaq-p/2251454 ( samuel gatica's ) , but the time is not precise , like the ticket created is 7 H but the time logged can already be 2D 7M , something like that . 
can someone help me with that , Thank You.

[Vitalii_Bobak_SaaSJet]

Hi @Nico 

If you are interested in report that shows time spent in the status, option can be Time in Status. To get report like this just:

1. Choose Project, Assignee, Sprint etc.
2. Filter issues by Time Ranges
3. Enjoy you report as Table or Chart view. 

You can also book a live demo - we'll show you the application inside out and answer all your questions.

Add-on also developed by my team.

I hope you find this helpful 🚀

[Hannes Obweger - JXL for Jira]

Hi @Nico

do I understand correctly that you want to track the time between the issue being created and the issue being moved into In Progress? 

This should be possible using Automation (see e.g. here) - but I feel it could be tricky to write it into the Time Tracking field. Is that a hard requirement for you? Otherwise you could also write the time into your own custom field.

Alternatively, as mentioned, there's a number of Marketplace apps that operate in this space - either automated time tracking, or time in status reporting. Happy to elaborate if that's something you might be interested in.

Best,

Hannes

[Hannes Obweger - JXL for Jira]

... and just to expand on the above:

If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of so-called history columns that aren't natively available, including the time in [status], time between [status] and [status], and many, many more.

This is how it looks in action:

As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting. Of course, you can also export your data to Excel or CSV in just two clicks.

Any questions just let me know,

Best,

Hannes

[Marc - Devoteam]

Hi @Nico 

As stated in the referenced community post, this would require a 3rd party marketplace app.

The automations suggested are good, but Yes time logged could be longer, depended the time the issue would have been in statuses before In Progress.

[Mehmet A _Bloompeak_]

Hi @Nico ,

Could you please clarify your request a little bit more? Are your looking for to

1. get the time passed since the issue created till the issue is transitioned to "In Progress" status
2. or get the time passed while the issue stayed in "In Progress" status and then automatically log work using this value.

[Nico]

Hi @Mehmet A _Bloompeak_ ,

It is no.2 , but i want to try to use only with Jira Automation , no third party app if i can.

Thank you.

[Mehmet A _Bloompeak_]

For no.2, you need a custom field and 2 automation rules.

• 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}}
• In the second automation:
  
  • Rule name: Calculate and worklog 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: Log work
    
    • Time Spent: {{NumberOfSeconds}}
    • Started: {{In Progress Start Time}}

[Marc - Devoteam]

HI @Mehmet A _Bloompeak_ 

I like your solution and this will work.

[Nico]

Hi @Mehmet A _Bloompeak_ 

I have tried your solution for the automation , so it doesn't automatically calculate the time that is currently running in the IN PROGRESS status ? and it will calculate the time when it is transistion to other status ?

 

[Nico]

and it will show like this ?

[Mehmet A _Bloompeak_]

Hi @Nico ,

The second automation calculates the time passed in "In Progress" status, but it does not store it in a custom field. Instead it directly creates a work log using the calculated time. That was your initial requirement.

If you also want to see the calculated time in a field then

1. Create Number type custom field named "In Progress Duration"
2. Update the second automation as below:

• Rule name: Calculate, Store and worklog 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}}
• Rule action: Log work
  
  • Time Spent: {{NumberOfSeconds}}
  • Started: {{In Progress Start Time}}

[Nico]

Hi @Mehmet A _Bloompeak_ 

I have problem for the logged part , it seems that the time between the logged and ticket created isn't the same time , can you help me with the problem?

as the screenshot i provide , there is 2 ticket , 1 is created 2 days ago and the other almost 2 weeks , but for the time logged for the no. 1 didn't popped the time tracking and for the second one it popped but the time seems not correct .

[Mehmet A _Bloompeak_]

Hi @Nico 

Both issues are still in In Progress status. Therefore our second automation rule did not execute yet. Once you transition them to next status in your workflow 2nd automation rule will execute and will create worklog.

The comment on the 2nd issue is created 4 days ago by your initial automation rule you mentioned in your original question above.

[Gizem Gökçe _OBSS_]

Hello @Nico ,

If you want to calculate the time spent in each workflow status automatically, you’ll need to use a third-party app that specializes in such metrics.

One such app is Timepiece - Time in Status for Jira, the oldest and leading 'Time in Status' app in the Atlassian Marketplace, developed by my team at OBSS.

Timepiece mainly allows you to see how much time each issue spent on each status or each assignee. 

In Timepiece, you can create a Status Duration Report: to automatically calculate how much time each issue spent in each workflow status, such as To Do, On Progress, etc. Also you can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

If you want you can display these insights on your Jira dashboard using the Timepiece Dashboard Gadget. In addition to this you can export reports in CSV or XLS formats for further analysis or sharing with stakeholders.

Timepiece is available for both Jira Cloud and Data Center. Let me know if you’d like help setting up this report or need more information! If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem