nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Time in Source Status Calculations

Prakhar Raj_2er2a8

Hi ,

I am creating a report for "Time in Source Status" for all transition. i have fetched the details using changegroup and changeitem however the issue is that some transitions are recorded with a difference of 1 hour from UI and some records are recorded without time difference which is leading to inconsistency in report.

i can't see any pattern for those transitions which are having no difference with UI hence i can't add\substract 1 hour in order to make the report accurate.

Is there way by which it can be fixed? is there any way by which we can get "Time in Source Transition" somewhere in jira database so that i can pick whatever it is present ?

Thank you in advance

Accepted answers

Fabian Lim

Other plugin options would be the Structure Plugin: https://wiki.almworks.com/display/structure/Time+in+Status+Column or eazyBI reporting: https://wiki.almworks.com/display/structure/Time+in+Status+Column

The most cost effective and easier to use would be Time In status.

All comments

Rahul

Hi @Prakhar Raj

If you would be interested in a ready made solution, you may want to try out our plugin,

Agile Tools : Epic Tree & Time in Status

It provides 3 major functionalities in one add-on

Multiple Time in Status Reports
- Time in Status
- Time with Assignee
- Time in Status with Assignee
- Time with Assignee per Status
- Status/Assignee Count
- Multiple Transition Reports
Epic Hierarchy / Sum Up (Standard Jira Hierarchy Epic -> Story -> SubTask)
Link Hierarchy / Sum Up (Hierarchy based on your issue link, upto 10 level deep)

Fabian Lim

The most cost effective and easier to use would be Time In status.

Mehmet A _Bloompeak_

Hi @Prakhar Raj ,

As an alternative, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count. The reports are based on history of issues and you can trim the history range.

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. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project). And all these are available as gadgets on the dashboard too.

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

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

Emre Toptancı _OBSS_

Hello @Prakhar Raj,

If there is a discrepancy between what you see on the screen and what is recorded in the database, the difference might be related to timezones. Please check that your users (both Jira user profiles and user computer's settings) are set to the correct time zone.

Based on the timezone of your users and the version of your Jira, even selecting the correct timezone might be inaccurate too. This is something we experienced in our country. Our country changed the daylight saving policy a few years back and decided to stay in Daylight Saving Time all year long. Jira uses a date library called Joda Time under the hood and older versions of that library did not know about this change so Jira was always changing all saved dates to one hour ahead or one hour behind (depending on the time of the year). Updating the Joda Time library corrected the issue for us.

Having said all this I should also note that 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. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time, or Lead Time.

You can calculate averages and sums of those durations grouped by the issue fields you select. (For example, see the total InProgress time per Epic or average Resolution Time per issue type).

Below are screenshots that show a custom Lead Time field that shows the total of ToDo and InProgress statuses. The same can be done for any status combination.

tisCloud_StatusDuration_LeadTime_with Estimates.png

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.

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 (released for cloud, server&DC gadget coming soon)

https://marketplace.atlassian.com/1211756

EmreT

Zoryana Bohutska _SaaSJet_

Hi @Prakhar Raj

Hope you have found the best solution for you, but for those who are still looking for a solution Time Between Statuses (created by my team) can also help. It allows set start and stop statuses for time calculation.

Regards

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

atl-gruland