Jira Progress Bar: How to Track Issue Progress Visually

The problem: Jira shows status, not progress

Jira is excellent at tracking state — a ticket is either To Do, In Progress, or Done. But state and progress are different things. An issue marked "In Progress" could be 5% done or 95% done. A sprint with ten "In Progress" tickets tells you almost nothing about how close you are to shipping.

Teams work around this in different ways: adding percentage fields manually, reading subtask counts, or running JQL reports. None of these give you a quick visual answer in the list view or on a dashboard.

A Jira progress bar solves this by surfacing progress as a visual element — directly on the issue, in list view columns, and in dashboard gadgets.

Three types of progress bar for Jira

Not every issue tracks progress the same way. A design task has different checkpoints than a bug fix, which is different again from an epic with ten subtasks. That's why it helps to have three distinct field types available:

1. Manual progress bar

You set the percentage yourself by dragging a slider. Simple and completely flexible. Useful for creative work, tasks with subjective milestones, or any situation where completion isn't determined by system events.

Best for: design tasks, content creation, research, discovery work.

2. Status-based progress bar

Maps your Jira workflow statuses to percentage values. When the issue moves from "To Do" to "In Progress" to "Done", the bar advances automatically. Zero extra clicks required.

You configure the mapping once in Admin Settings — for example:

• To Do → 0%
• In Progress → 50%
• In Review → 75%
• Done → 100%

After that, the bar updates every time someone changes the issue status. No manual input needed.

Best for: sprint tickets, bugs, standard development tasks — any issue that moves through a defined workflow.

3. Subtask-based progress bar

Calculates resolved subtasks ÷ total subtasks automatically. No setup required beyond adding the field — it reads Jira's own subtask data. The field also shows the raw count ("2/3 done") next to the bar.

Best for: epics, stories with subtasks, QA checklists, multi-step tasks, onboarding flows with child issues.

All three field types on a single issue — Manual (70%), Subtasks (83%, 2/3 done), Status (50%, In Progress)

Progress in the Jira list view

The real power isn't on the individual issue — it's when you add progress fields as columns to the list view or backlog. Each field type gets its own column: you can show Manual, Status-based, and Subtask-based side by side, or just the one that fits your workflow.

The columns display a colored dot and the percentage value. Red is immediately visible — a sprint with three red dots at 10% on day four of five is a risk signal that no status column would surface this clearly.

Three progress columns in the Jira list view — each field type has its own column with a color-coded dot and percentage

How to set up a progress bar in Jira

The following steps apply to Visual Progress Tracker for Jira, available on the Atlassian Marketplace. The app is built on Atlassian Forge, so it runs entirely on Atlassian's own infrastructure — no external servers, no data leaving your Jira site.

1. 1
   Install the app from the Atlassian Marketplace. Free trial available, no credit card required.
2. 2
   Go to Jira Settings → Custom Fields. Create a new custom field and select one of the three progress bar types: Manual, Status-Based, or Subtask-Based.
3. 3
   Add the field to your project screens. Jira will then display the progress bar on all relevant issue views in that project.
4. 4
   Add the field as a list view column by clicking the column header area in any Jira list or backlog. The progress bar is now visible across your entire project at a glance.
5. 5
   (Optional) Add the dashboard gadget. The Progress Tracker Overview gadget gives team leads a summary table of every issue in a project, sortable by progress value.

For Status-Based fields, one additional step: go to App Settings → Status Mappings and assign a percentage to each of your workflow statuses. After that, everything is automatic.

Color thresholds: when does a bar turn red?

By default, the color coding works like a traffic light:

• Red: 0–33%
• Yellow: 34–66%
• Green: 67–100%

These thresholds are configurable in Admin Settings. If your team considers anything below 50% at-risk, you can adjust the yellow/green boundary accordingly. The color change propagates immediately across all views — list, issue detail, and dashboard.

Frequently asked questions