Time in status showing incorrect data in transition rab of Activity section

[khushboo_puri]

In the activity section there are various rabs like transition which is showing incorrect data for time in status as 3 months where as when is showing 27 Aug 2023.so it should show 2 years but time in status showing 3 months...for open-> in progress transition

[Birkan Yildiz _OBSS_]

Hey @khushboo_puri 

Jira’s native Time in Status reports can be problematic. There are no custom calendars, report types are limited, and export restrictions often make it hard to get accurate data.

If you’re open to a Marketplace app, you might want to check out Timepiece – Time in Status for Jira. It has custom calendars, provides accurate Cycle Time, Lead Time, and SLA metrics, and goes beyond worklogs with flexible reports (Time in Status, Assignee/Group Time, Duration Between Statuses, Status Count, etc.). You can also automate reporting with Scheduled Reports & Alarms, and integrate everything via its REST API.

The best part is that Timepiece works directly with your existing Jira history. So there is no need to create custom fields or update anything manually. You can start generating reports right after installation.

Happy to answer any questions if you’d like to learn more.

Disclaimer: I work at OBSS, the developer of Timepiece.

[Iryna Komarnitska_SaaSJet_]

Hi @khushboo_puri !
It’s a little difficult to understand exactly what you mean — could you perhaps share a couple of screenshots so I can see the case more clearly?

In theory, the behavior could be explained like this:

• The first transition to In Progress may have been on 27 Aug 2023 (about 2 years ago).

• But if the issue later left In Progress and then re-entered it (for example, 3 months ago), the “Time in status” counter resets at that latest entry.

• As a result, Jira shows 3 months — because that’s how long the issue has been in In Progress this time, not the total across all periods.

If you want to get that complete picture, there are marketplace apps that extend Jira’s reporting. One of them is our own Time in Status app — it was designed specifically to calculate and aggregate these periods automatically. With it, you can:

• See cumulative time spent in each status (not just the latest stay).

• Analyze how long issues stay in bottleneck statuses like “In Progress” or “Review.”

• Export reports or build dashboards to share this data with your team.

This way, instead of just seeing “3 months,” you can understand the real 2 years total the issue has been in In Progress across all cycles.