Jira Cloud app · Flow metrics
Average Task Completion Time in Jira: cycle time by issue type, per sprint
How long does a bug really take compared with a story? PM Overview measures task completion time between the board columns you pick, so you can find where work waits and improve your estimates.
- ★ 5.0 on the Atlassian Marketplace (17 reviews)
- Free for teams up to 10 users
- 30-day free trial for any team size
- Scrum and Kanban boards
- Opens inside Jira Cloud, no setup
In short: PM Overview’s Average Task Completion Time charts measure how long Jira issues take from a start column to an end column you choose (for example In Progress → Done). Results are shown per issue type (story, task, bug) and per label or epic, for each sprint or custom timeframe, in hours or days.
Why completion time matters more than you think
- Better estimates. If bugs average 2 days and stories 9, you can plan a sprint with real numbers.
- Find bottlenecks. A sudden jump in completion time points at a blocked review, test or deployment step.
- Better retrospectives. Compare sprints on data instead of feelings.
- Credible delivery dates. Stakeholders get forecasts based on how long work actually takes.
What you can configure
| Setting | Options |
|---|---|
| Start time | Any column on your board (for example “In Progress”) |
| End time | Any column on your board (for example “Done” or “Released”) |
| Unit | Hours or days |
| Data source | Sprint (default for Scrum), backlog (default for Kanban), or both |
| Timeframe | Current sprint, previous sprints or a custom date range |
| Breakdown | By issue type (story, task, bug), or by label and epic |
Native Jira vs PM Overview
| Native Jira Cloud | PM Overview | |
|---|---|---|
| Cycle time by issue type | Control Chart with manual filtering | Built in, per sprint |
| Choose start and end columns | Yes, in Control Chart | Yes |
| Breakdown by label or epic | No | Yes |
| Next to velocity and sprint progress | No, separate report | Yes, same dashboard |
| Hours or days | Fixed | Your choice |
Up and running in 2 minutes
- Install PM Overview from the Atlassian Marketplace. It is free for up to 10 users, and every team size gets a 30-day trial.
- Open your Jira project and click PM Overview in the project navigation (or under More).
- Pick a board and sprint. The dashboard fills itself from your existing Jira data. No gadgets, JQL or spreadsheets to set up.
What teams say on the Atlassian Marketplace
Great to use so far. I was looking for a time tracking and resource allocation dashboard.
Charles Smith, Marketplace review, Sep 2025
We were looking for this kind of plugin, one view to manage our project. Also helps with reporting and retrospectives.
Marketplace review, Aug 2024
This dashboard is exactly what we were looking for!
Sarah, Marketplace review, Jul 2024
Frequently asked questions
How do I measure average task completion time in Jira?
Jira Cloud’s Control Chart shows cycle time for a board, but not broken down by issue type in a simple view. PM Overview calculates average task completion time per issue type (story, task, bug) for each sprint or timeframe, between the board columns you choose.
What is the difference between cycle time and lead time?
Cycle time measures from when work starts (for example “In Progress”) to when it’s done. Lead time measures from when the issue was created to when it’s done. In PM Overview you set the start and end columns yourself, so you can measure either.
Can I show completion time in hours instead of days?
Yes. Choose hours or days as the unit in the side panel settings.
Can I break completion time down by label or epic?
Yes. A second chart groups completion time by labels and epics, so you can see which kinds of work take longest.
Is PM Overview free?
PM Overview is free for Jira Cloud sites with up to 10 users. Larger teams get a 30-day free trial and then pay per user through Atlassian.
See how long your work really takes
Install PM Overview and get average task completion time per issue type for every sprint. Free for up to 10 users.
