Can we capture log work during transition of every status automatically?

[shravya chinthapatla]

Hi Team,

I have a time spent field as mandatory during transition of every status. Currently log work is provided by Assignee manually after every stage, Is there a way in JIRA to track time spent in every status automatically so that the log work can be effective and avoid manual time tracking.

[Karolina Wons_SaaSJet]

Hello @shravya chinthapatla 

Additionally to the existed comment, I can advise trying Time in Status for Jira Cloud. As for me, it's the most convenient way to track time spent in each status automatically.

It also allows getting how much time each assignee has spent working on each issue and exporting data to CSV or XLSX files.

This add-on is developed by my team, please, let me know if you have any questions.

Hope it helps

[Emre Toptancı _OBSS_]

Hello @shravya chinthapatla

Instead of creating worklogs for this, you can get direct reports about how much time was spent on each issue. Jira holds this data in each issue's history. You will need a marketplace app to get ready-to-go reports about this.

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee.

       

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

Time in Status has Custom Calendar function which allows you to create as many different working calendars as needed and get reports based on them. 

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 (organization) 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. It supports both Company Managed and Team Managed projects.

Time in Status 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.

  

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 issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

[Mehmet A _Bloompeak_]

Hi @shravya chinthapatla

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. 

• This app has a dynamic status grouping feature so that you can generate various valuable reports as as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

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

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

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters

Hope it helps.

[Walter Buggenhout]

Hi @shravya chinthapatla,

Tracking time 'automatically' would basically mean the time spent between status transitions. That information is already available in issue history; you would only need to look at e.g. the control chart or a reporting tool to expose that information.

Tempo Timesheets also has a tracker that can automate time tracking by just starting and stopping a timer.

Usually, though, the actual time users spend on tasks are not 100% on one single task. So there is a difference between the time an issue actually spends in a status and the real time it is being worked on. From that perspective, manual logging of time is not necessarily a bad thing.

Hope this helps!

[Rob_Huntley_Tempo]

@shravya chinthapatla  to follow up on @Walter Buggenhout 's comment - Tempo does have a tracker that can start and stop time while working on an issue - but as Walt, rightly points out, we often do more than one thing at a time etc.

Tempo also has an activity feed than uses machine learning to observe, analyze and suggest where an employees time is spent.  This makes for more accurate accounting of an employees time spent on issues in Jira, develop work in platforms like JetBrains or Visual Studio.  

You can then take that accurate data from Tempo Reports, along with account and billing information and export it for you own needs.

https://help.tempo.io/cloud/en/tempo-timesheets/logging-your-time/logging-time-in-my-work/logging-time-using-the-activity-feed.html

Rob Huntley

Tempo Product Expert