Time tracking of Task

[Sian Snook]

Is there a way of automating the time a task , story or epic took to completed without a user added "Time Tracking' or 'Actual time' etc

Instead of user manually adding the time took in a field..

Can you take time from somewhere else?

just watched this its til logging time any way of automating from the backend of time?

https://www.youtube.com/watch?v=P_O9tKLQUTw

[Gizem Gökçe _OBSS_]

Hello @Sian Snook ,

As @Walter Buggenhout noted OOTB Jira requires Jira users to log time to track time spent. If it is not possible for people to enter logs into the system, I suggest you track the time spent on each status or assignee in a Jira workflow to get clearer measurements.

For this I want to suggest a Marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has several report types that will meet your need.  Our app is available for both Jira Cloud, and Data Center. 

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

Status Duration report which shows how much time each issue spent on each status. 

Assignee Duration report which shows how much time each assignee spent on each issue. 

 If you want a combination of these two you can use Assignee Duration per Status or Status Duration per Assignee reports.

he 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. 

Visit Timepiece - Time in Status for Jira to experience the full range of features.

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

[Madhu_RVS]

Hi @Sian Snook 

I believe the best way would be to track the time the issue spent in each of the statuses and then add up the total time spent in each status to calculate the issue completion times. You can use Jira Rest APIs to pull this information from issue changelogs or also write automation scripts to populate a custom field each time the issue changes its status. Another option could be to use a mktplace app. If you are open to try one take a look at 

Time in Status Reports 

With this app you can generate time in status for multiple issues from multiple projects. You can also group your statuses to define your own cycle / issue completion times. The app can easily be added as a dashboard gadget too.

More details here.

Disclaimer : I work for the vendor who built this app

[Walter Buggenhout]

Hi @Sian Snook,

Out of the box, Jira lets you use the original estimate / time spent / remaining estimate fields to track time or effort. It does not offer features to track this automatically, but there are many time tracking apps in the Atlassian Marketplace - some of them have trackers that can be started and stopped to automatically track time spent.

If you start looking into them, I would recommend you to think beyond just this automated tracking requirement, but also about reporting requirements, the need for an approval mechanism for employee timesheets, the capability to use timesheet data for invoicing or integration with billing systems, ...

This is an area where an investment in a good marketplace app may add some significant value to your Jira instance.

Hope this helps!  

[Sian Snook]

Any way are going it without an App?? cant add them as am not a site admin?

[Wojciech Wardaszko]

@Sian Snook 
If you want automated time tracking without an app, you could try using Jira Automation. I'd do it like this:
Create a custom field of type "date picker with time" and call it Last active transition timestamp
Have one rule update the field with {{now}} when transitioned to an active (blue) status.
Have another rule log work for the assignee when transitioned from active status, and the time to log should be

{{issue.Last active transition timestamp.diff(now).minutes}}m

The start date should be simply

{{issue.Last active transition timestamp}}

Please keep in mind that this is not foolproof, and some scenarios (like a series of quick transitions or issues left in active status overnight) might produce unwanted results. It will also burn through your automation execution limits, so I'd strongly recommend considering an app like our Clockwork Free or Clockwork Pro, which comes with timers, automated time tracking based on transitions, great timesheet reporting, and much more!

I hope this helps.

Cheers!