Any way to track/report/visualize a single work item's progress through statuses from creation to do

[Claire Abt]

We have a relatively straightforward workflow progression defined, but have an "Input Required" status for questions, stalls, etc. 

Work items start development, move through to QA, and frequently, a back-and-forth takes place. Depending upon timing (we have a distributed world-wide team), the  work item may spend a day or more in Input Required. Again, depending upon timing, the item may move in and out of Input Required more than once.

We would like a way to track the workflow transitions of single work items.

I can go into the history and manually copy out the date/time of each transition, but is there any better way? Are there any predefined reports, or has someone else come up with sometime a little more elegant? 

Thanks!

[Iryna Menzheha_SaaSJet]

Hi @Claire Abt 👋
Welcome to the Community!

You're absolutely right — manually pulling transition timestamps from issue history is time-consuming (especially with back-and-forth status changes like “Input Required”).

Option: Time In Status

This app is great for exactly what you're looking for — it gives a detailed breakdown of how long each issue spent in each status, including multiple entries into the same status.

With Time in Status, you can:

• View all status transitions (with timestamps)

• See how many times the issue entered a status like “Input Required”

• Track time spent per status and visualize the flow

• Export the data to Excel or share as a dashboard gadget

Also app give you access to Sprint Performance Report. This report contains various metrics for each sprint, including Team Velocity.

So instead of digging through history logs, you get an elegant timeline and time metrics automatically.

App developed by my team.
Have a nice day and happy sprinting 🥳

[Rahul_RVS]

Hi @Claire Abt  

Welcome to the community !!

If you would be interested in a mktplace app for this requirement, you can try out

Time in Status Reports 

For your specific need the Status Transition details report can help. It shows the transitions the issue went through and on which date as well.

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. The app has 20+ reports to meet a variety of use cases.

More details here.

Disclaimer : I am part of the app team for this add-on

[Sanam Malleswari]

Hi @Claire Abt

Welcome to the Atlassian community!

Please try below options.

• Control Chart (Reports > Control Chart) – If you're using a Jira Software board, this shows how long issues spend in each status. It’s great for spotting delays, especially if items get stuck in “Input Required”.
  View and understand the control chart | Jira Cloud | Atlassian Support

• Marketplace Apps – Tools like "Time in Status by OBSS" or "Status Time Reports" let you see:

  • How long an issue stayed in each status

  • How many times it transitioned in/out

  • Visual reports and exports (CSV, Excel)

[Claire Abt]

thanks -- yeah, the control chart is great, but as i noted below, i'd really like to track by work item. if there's a way to configure the control chart to share this information, that'd be really appreciated.

for instance, i have a work item that we created 2 months ago, but had unresolved questions. we put it in Input Required status, even though it was not in a sprint. we finally got the responses and brought the item into a sprint. 

that item was in Input Required for 20 days outside of the sprint. although i've limited the control chart timeframe to the past two weeks, that issue is showing that it was in Input Required for 20 days, even though it's progressed well through the sprint workflow.

if i could limit the control chart to only the specified sprint, that might be helpful. 

thanks!

[Ayça Erdem_OBSS_]

Hello @Claire Abt 

Welcome to the community 

It sounds like you're trying to monitor how your work items move through the workflow, particularly how often they enter the Input Required status and how long they stay there — especially in cases where tickets go back and forth multiple times.

Jira’s issue history does contain this information, but extracting it manually for every transition is time-consuming and error-prone.

If you're open to using a Marketplace app, I’d recommend checking out Timepiece - Time in Status for Jira, the oldest and leading “Time in Status” app in Atlassian Marketplace, developed by our team at OBSS. Timepiece works with Jira Cloud, Server, and Data Center, and calculates reports using Jira's existing issue histories — no workflow changes or data prep required.

Here's how Timepiece can help:

Timepiece offers multiple reports that can help you analyze how often and how long an issue stays in a status like “Input Required”. Here's a breakdown of the most relevant ones:

• Drill Down Report – Shows every status transition with exact timestamps and durations, ideal for tracking repeated entries into “Input Required”.

• Status Duration Report – Calculates the total time spent in each status (e.g. “Input Required”), even if entered multiple times.

• Transition Count Report – Displays how many times an issue transitioned into each status, useful for identifying churn or back-and-forth.

Each of these reports can be filtered to focus only on the statuses you care about and can be grouped by assignee, project or even by time periods (e.g., per sprint, week, or month).

Timepiece 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. Also you can export the reports in to various formats easily. 

You can visualize the results both as tables and charts, and use them to compare trends over time or across teams.

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace.

Hope it helps!

Ayça 

[Danut M [StonikByte]]

Hi @Claire Abt,

Welcome to the Atlassian Community. 

The Jira's Control Chart report could be a option. It can show the time in status for individual issues. And I think you control the issue displayed in the chart, by using its "Quick filters" option under Refine report section.

 

For something better, you could look for an app on Atlassian Marketplace. 

In case you want to try an app, our Great Gadgets app offers some gadgets that could be useful for your use case.

Control Chart gadget - similar to the Jira's Control Chart report, but more advanced and highly configurable. Allows you to specify a JQL/filter with the issues that you want displayed in the chart. You should configure it to calculate the cycle between entrance in "Input Required" status and the entrance in a difference status or status category.

 

On its Data tab, it can display the list of individual issues and their cycle time. Can exclude weekends from the calculation. 

Time in Status gadget - lets you measure the time in status for issues in a JQL/filter. 

On its Data tab, it can display the list of individual issues and the time spent in each status. can exclude weekends from the calculation. 

If you have any questions about these gadgets, feel free to contact us directly at support@stonikbyte.com. 

Danut. 

[Claire Abt]

thanks, folks, for the feedback. i'm really trying to figure out how i can report/visualize the flow of an individual work item over the course of a sprint. for instance, this is a (dummy) sheet that shows the progress of 3 items over the course of a 2-week sprint. color coding is optional.

while i can (and do) monitor the sprint board, etc., there is no clear reporting mechanism for this. i want to be able to track, over time, work items that have questions at the beginning of a sprint to help the team with story writing, refining and commitment, and also items that have repeated back and forth during the sprint to perhaps identify other areas for improvement.

does this help better explain my original request? thanks!

[Neil Fletcher]

Hi @Claire Abt 

A variation of this filter might help... several filters could then be used and added to a dashboard to visualize;

status CHANGED FROM "QA" TO "Input Required" BEFORE endOfWeek() AFTER startOfWeek()

this will return transitions this week from one status to another - you can check the results in the work-items history