Report on Progress of Tickets through Sprint

[Eric Lynch]

Hi,

I'm looking for a solution that show the progress of the tickets through the sprint. The burndown chart is binary and gives you "credit" when the ticket enters a resolved status or the right most column on the sprint board.

However, I'm looking for a way to report the progress of the tickets through the various columns. I don't know of a way to do this in Jira and I understand columns set up is merely just a UI thing (save for the 3 statuses you get with To Do, In Progress and Done).

Am I missing something or is there a marketplace app I can bolt onto Jira that can help?

Here is an example screenshot of what I showed my team just today, but it required exporting and data manipulation.

Thanks!

Eric

[Valeriia_Havrylenko_SaaSJet]

Hi @Eric Lynch  ,
Welcome to the Atlassian Community!

If you don't mind looking at other apps, you can try Sprint Report from Time in Status app, which my team developed. 

The report gives Scrum teams a detailed overview of sprint activities and data. It’s an invaluable tool for tracking progress and performance from completed sprints, empowering teams to make well-informed decisions.

It contains the following main charts: Team Velocity, Workload, Completion rate, Committed, Completed, and Scope change.

I hope you find it useful.

[Mehmet A _Bloompeak_]

Hi @Eric Lynch ,

As @Danut M _StonikByte_  mentioned, you can achieve this using the built-in Two Dimensional Filter Statistics and Issue Statistics gadgets. But you need 3 different gadgets.

If you're considering using a marketplace app, you can try the 'Reports - Charts and Graphs for Jira' app developed by our team. It provides the bar chart, as shown below.

Here is our live demo dashboard where you can see and modify sample reports and play with them.

If you are looking for a free solution, you can try the limited version Reports - Charts and Graphs for Jira Dashboard Free.

If you have any questions, feel free to schedule a demo with us.

[Mehmet A _Bloompeak_]

Another alternative might be using Sum Up Reports for Jira app developed by our team. It provides bottom line sum ups.

[Alexey Pavlenko _App Developer_]

Hi @Eric Lynch ,

If you are open to other views as well, you can consider the 3rd party app I developed -  Multi-team Scrum Metrics & Retrospective. With it, you can get this:

Or this view with statistics:

You can add as much statuses/custom JQL filters as you want.

Best regards,
Alexey

[Ayça Erdem_OBSS_]

Hello @Eric Lynch 

Welcome to the community 

The table you shared makes perfect sense—you’re trying to track how tickets progress through various stages during a sprint, but Jira’s Burndown Chart only reflects when an issue reaches a resolved status or the last column on the board. Since Jira's board columns are mainly for UI representation, there’s no built-in way to analyze the detailed movement of issues across all statuses.

How Timepiece - Time in Status for Jira Can Help

Instead of manually exporting and manipulating data, Timepiece - Time in Status for Jira, developed by our team at OBSS, can automatically generate reports similar to the table you shared.

• Status Duration Report – This shows how long each issue spends in each sprint stage, giving you visibility into ticket progress.
• Duration Between Statuses – Tracks how long it takes for issues to transition from one stage to another, helping identify slow-moving stages.
• Customizable Metrics – Filter and group data by sprint, issue type, or assignee to get deeper insights.

Here is an image showing status duration reports in the sprint

This way, you get real-time tracking of sprint progress without needing to manually export and manipulate data.

For a deeper dive into how  Timepiece Sprint Reports can help optimize your Agile workflows, check out our article here:
Optimize Agile Workflows with Timepiece Sprint Reports

If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features.

hope it helps

Ayça

[Danut M _StonikByte_]

Hi @Eric Lynch,

Welcome to the Atlassian Community. 

Jira offers some dashboard gadgets that could be helpful: Two Dimensional Filter Statistics and Issue Statistics gadget. If you configure them with a filter that returns the issue from your sprint, you will get such stats based on issue count. Unfortunately these gadgets cannot provide stats based on sum of story points, but still they will cover your need in some extent. 

If you want stats based on sum of story points, then you will need to search for a plugin on Atlassian Marketplace.

In case you want to try a plugin, our Great Gadgets app offers a Pivot Table & Pivot Chart gadget that let you generate tables, heat-map tables, charts in the format you want. It works like the pivot tables in Excel.

Unfortunately this gadget cannot display stats by count, story points and percents in the same table. You should add multiple gadgets side-by-side.  

Danut. 

[Vishal Biyani]

@Daryl Marsh 

if you want to aggregate story points from Standard Issue Level to Epic, you will need to write an automation to do the rollup. JIRA does not do that out of the box.

Could you list down the columns that you want to report on?

Can you clarify the last column that shows % is that Progress % column provided by JIRA or a custom field defined in your project?

Have you looked at two dimensional filter and Filter Results gadgets that can be added in the dashboard?

[Petru Simion _Simitech Ltd__]

Hi @Eric Lynch ,

Boards are views into the data.

Each column can be mapped to one or more workflow statuses. 

Every company designs it's workflows potentially differently, even if some are probably similar when dealing with established processes.

However Jira allows this complex mapping of statuses to columns, coming from various workflows associated with various issue types.

When you want a solution that "shows the progress" of a ticket from inception to finalization, you might mean you want to see

1. When and how the issue was moved from one column to the next
2. How long it took for the issue to reside in either of the columns

Or maybe both.

Implementing an automated solution might prove challenging and might not meet your need to have a report that you can later analyse. Also such a solution will only start working on issues created after the automation was implemented.

You could attempt to make REST API calls and extract this data from the issues history, then manipulate the data that comes in JSON format to your needs.

If you are open to using apps, you could use one of the following apps released by our company.

• For point one you could use Issue History Dashboard for Jira .

You can search for all issues by project or filter out using various fields.

The result is in a tabular format, with searcheable columns and exportable in csv format.

Because you are interested in how/when issues are being transitioned between columns, and that means between workflow statuses, you can filter to search only for issue history changes where the updated field was the 'Status'.

For example, the following search retrieves a specific Story in project Apple and only for history changes where the field Status was updated. You can sort by Date of Change and there you have the way that issue was transitioned and when from one status to another.

Deppending on how those statuses are mapped to your board columns you can have a picture of the way the issue moves on the board between columns.

• For point two

I you are also intrested in how long did the issue spent in each of the statuses, in other words, in a column of the board, you could calculate these values from the issue history extracted at point 1, between different Date of Change.

However, if you could benefit more from an app that already calculates the time spent in each status, you could use Time in Status Dashboard for Jira .

You can filter your searches by project, issue(s) and other criteria.

The result will show how much time each issue spent in each status as well as how many times the issue was present in the status.

Two perspectives are available, facilitating the way data will suit you better.

The columns perspective presents each issue in a row, and the time spent in each status is represented in columns.

The rows perspective presents each time spent in status value in a row.

Both perspectives have sortable columns and are exportable to csv for further analysis, charting etc.

Deppending on how statuses for each issue type are mapped to your board columns, you could in Excel add formulas to use the time spent in status for various statuses.

Once you developed your formulas you can just keep exporting from this app and apply the calculations in the Excel formulas for the final data format that you desire.

Regards, 

Petru

[Daryl Marsh]

Eric,

The active sprint kanban provides most of this information already, as long as your columns are setup correctly.

In my attachment, the red circle represents the number of issues in a status. The cards can be configured to display story points, the yellow highlight.

Hope this helps.

-Daryl

[Eric Lynch]

Thanks @Daryl Marsh

I see your point here on issue count but where is the aggregation of the story points happening? That still seems like a manual exercise.

Also, the status categories I have in my screen shot are not necessarily the columns I have on my board. I have simply broken down the build SDLC into these categories to help illustrate how things are progressing in the sprint. In actuality we have way more columns on our active sprint board.

[Daryl Marsh]

Unfortunately those values cant be aggregated on the board. I was simply suggesting an alternative to having to create a report on a dashboard.

If you havent figured out an automated way of 'grouping' your status together, you could use a label that gets applied as the issue transistions - for example a 'Build complete' label gets applied when a issue transistions to a status you consider 'Build Complete'. You can then use this label to filter your report. Just keep in mind to clear any labels you dont want before the new one gets added.