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; } } }

Looking for a way to monitor quarterly progress in Jira

Eran Roiter_tdmgcu

Hi all,

I’m looking for a tool or method within Jira that can help monitor progress throughout a quarter.

For example, let’s say a team has 10 Epic's planned for Q2, each with about 10 story points. As we progress through the sprints, story points are gradually completed.

Is there a way in Jira to see, at any given moment, how we're tracking compared to where we should be in order to complete all committed work by the end of the quarter?

Ideally, I’d like to say:
“In Q2, we have 10 developers, which gives us a total capacity of around 100 story points per sprint. By Sprint 2, I can already see whether we're ahead, behind, or on track.”

Right now, I’m managing this manually outside Jira, which creates a lot of extra work—especially with large dev teams.

I’d really appreciate any advice, tools, or ideas that could help automate this process or at least make it more efficient within Jira.

Thanks so much, and have a great week!

Accepted answers

All comments

Murat Seven

Hi @Eran Roiter ,

To efficiently monitor progress throughout a quarter in Jira, you can utilize several tools and features available in Jira Cloud Premium;

Advanced Roadmaps:

Capacity Planning: This feature allows you to plan based on your team's capacity and velocity, ensuring that your quarterly goals are realistic and attainable.
Timeline View: Use the timeline view to visualize the progress of your epics and stories over the quarter. This view can be customized to show progress bars indicating the status of issues

Dashbıards and Reports:

Velocity Chart: This chart helps you understand your team's velocity by showing the amount of work completed in each sprint. It can help predict future performance based on past sprints.
Sprint Reports: These reports provide insights into the progress of each sprint, showing completed and remaining story points.

Single Sprint Overview Dashboard:

This dashboard template provides an overview of Jira sprints, including completed and remaining issues, changes in sprint scope, and issue status transitions. It can display data based on issue count or story points, allowing you to track progress effectively.
- https://support.atlassian.com/analytics/docs/sprint-overview-dashboard-template/

EazyBI Reports:

Consider using add-ons like eazyBI for more advanced reporting and visualization options. This tool allows you to create custom reports and dashboards to track progress against your quarterly goals.
- https://confluence.atlassian.com/jirakb/reporting-in-jira-461504615.html
- https://marketplace.atlassian.com/apps/1211051/eazybi-reports-and-charts-for-jira?tab=overview&hosting=cloud

Best regards,

Murat Seven

Eran Roiter_tdmgcu

@Murat Seven Thanks for the answer.

I saw what you wrote, but none of them are good enough.

I want to be able to set a X resources before the Q starts, and then have the option to compere it in any given time.

+ The EazyBI are very complicated to build.

Thanks !

Dick

Hi @Eran Roiter

If the roll-up fuction in the roadmap / plans view in Jira isn't what you search for, you could very well use a tool such as JXL to generate the desired listings (sheets). It allows you to create a sum-up line that can even show you the percentage of epics completed.

Kind regards,
Dick

Marc -Devoteam-

Hi @Eran Roiter

Your question is more BI related and yes EazyBI is complicated.

you could use the Jira API to get data out of the system or look at 3rd party apps that are able to export information to BI tooling like:

PowerBI, Tableau, other...

Alexey Pavlenko _App Developer_

Hi @Eran Roiter ,

I am the developer of Multi-team Metrics & Retrospective.

One of the solutions can be adding an option to my app that shows estimates of epics for all the work items in a sprint, alongside other sprint metrics, and displays an optimal burn-down trajectory (dark red line), which is calculated based on the velocity/completed scope for the displayed number of periods in this way:

Please let me know what do you think.

My app is also good for in-place retrospectives (take a look at the demo on the marketplace listing).

Best regards,
Alexey

Iryna Menzheha_SaaSJet

Hi @Eran Roiter ! 👋

You're raising a very relevant point — tracking quarterly progress across epics, story points, and sprints can be hard to manage manually, especially at scale.

Jira’s native velocity and sprint reports are limited when it comes to longer timeframes like quarters and don’t offer the flexibility needed to filter by epics, timeframes, or developers.

Alternative: Time In Status

If you’re looking to bring this process into Jira and automate progress tracking over a quarter, the Time in Status app can help a lot — and not just for time tracking.

Here’s how you can use app to monitor quarterly progress effectively:

🧩 How It Works

At the heart of Time in Status is the grid report – it’s a matrix that shows you how much time each issue spent in each status.
This is especially useful for quarterly tracking because you can:

📊 Track all Q2 epics/stories and see how long they stayed in statuses like Backlog, In Progress, Code Review, Done
⏱ Understand where time is actually spent (and where you’re slowing down)
📆 Monitor how work flows across sprints throughout the quarter
🔄 Export the full report to Excel for deeper analysis or stakeholder reviews

You can group data by assignee, epic, label, or sprint to match your Q2 planning structure.

📊 Sprint Report

You can:

Track what each developer committed, added, and removed during each sprint
Visualize completion % per developer or for the whole team
Use this data sprint-by-sprint to see how the quarter is progressing
Identify trends (falling behind or on track) based on actual vs. planned workload

This is especially helpful when you want to understand performance sprint-over-sprint, and how it impacts your quarterly goals.

🎯 Filtering Capabilities

You can apply flexible filters such as:

Project, assignee, label (e.g., “Q2”), issue type (like Epic or Story)
Sprint names or even custom fields
Date ranges — so you can focus only on issues updated during Q2

So if your team is working across multiple projects or sprints, you can still narrow your reports down to only Q2 epics and get a clear picture.

📥 Data Export + Dashboard Gadgets

You can:

Export data to Excel or CSV for detailed reporting or stakeholder presentations
Embed reports as gadgets on Jira dashboards to share with your team or management

This makes it easy to keep a real-time view of progress vs. your expected quarterly capacity.

🔁 Works Retroactively

One big bonus: Time in Status works with historical Jira data, so you don’t need to configure anything in advance. Even if you install it mid-quarter, it can still pull and report on all activity from earlier sprints.

Add-on developed by my team.

Let me know if you'd like help defining a filter or creating a report layout — happy to assist!

Viktoriia Golovtseva (TitanApps)

Hey @Eran Roiter

This is a common challenge, especially with quarterly planning and larger dev teams.

If you're looking to move away from manual tracking and gain a real-time view of how you're progressing vs. expected delivery, I highly recommend trying the free Smart Productivity & Team Performance Dashboard by TitanApps (available on the Atlassian Marketplace).

Screenshot 2025-04-16 at 10.54.23.png

Here's how it can help in your use case:

Track story point progress across Epics, Sprints, and Quarters
The dashboard shows how much work (e.g. story points or issues) has been completed vs. what was planned at the Epic or sprint level.
Visualize team capacity vs. delivery pace
You can define team capacity (e.g. 10 developers × 10 points/sprint = 100 SPs) and instantly see if you’re ahead, behind, or on track over time.
Drill down by sprint, project, epic, or issue type
Quickly identify where work is stalling or overperforming, and which teams are contributing what.
Aggregate data from Jira, GitHub, and Confluence
For teams working across platforms, you get a more complete picture of productivity beyond just Jira.
Ideal for quarterly planning, sprint retros, and OKR check-ins
With just a glance, you can understand whether your team will realistically hit targets by the end of the quarter—without building custom dashboards or exporting data to spreadsheets.

You can learn more about it here.

Hope this helps streamline your process and free up more of your time from manual tracking.

Rahul_RVS

Hi @Eran Roiter

If you would be interested in a mktplace app for this requirement, pls do take a look at
Agile Velocity & Status Gadgets

The app comes with few dashboard gadgets to track team member's / team's velocity / productivity based on story points / time spent / issue count in a sprint and also track sprint status with multiple parameters.

Disclaimer : I am part of the team which developed this app

Resource Velocity Chart.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

time-tracking

estimate

automation

story-points

roadmap

project-management

addon

tool