A Practical Guide to Jira Dashboard Gadgets for Agile Teams

Need clearer sprint insights? Use jira dashboard gadgets to track progress, workload, and blockers. Read now to build a focused dashboard.

A Jira dashboard can make sprint progress easier to understand, but the wrong gadgets can turn it into a cluttered wall of charts. If every team member sees different numbers or struggles to find the next action, the dashboard adds noise instead of clarity. That can lead to missed blockers, confusing status meetings, and decisions made with an incomplete view of the work.

Here’s the good news: a useful dashboard doesn’t need dozens of gadgets. A small set, chosen for a clear audience and purpose, can show delivery progress, workload, and risks at a glance. This guide explains what Jira dashboard gadgets do, which ones Agile teams often use, and how to arrange them into a practical view your team can maintain.

What Jira dashboard gadgets do

Jira dashboard gadgets are configurable panels that display project information, charts, saved-filter results, or Agile progress on a dashboard. Each gadget has a specific purpose, such as showing unresolved issues, visualizing sprint progress, or summarizing work by priority.

You can add several gadgets to a dashboard and arrange them to suit different needs. A Scrum team might put sprint progress near the top, while a product lead may prioritize incoming requests and delivery trends.

But here’s the truth: a dashboard is only useful when its gadgets answer questions people actually ask. A chart that looks impressive but doesn’t help someone decide what to do next is taking up valuable space.

Jira product screenshot

Know the building blocks

Gadgets: Panels that display selected information or visual summaries.
Filters: Saved Jira searches that determine which issues some gadgets show.
Dashboard layout: The columns and positions that affect how people scan the page.
Permissions: Settings that determine who can view or edit a dashboard and its related filters.

For example, a Filter Results gadget can list open blockers from a saved filter. A Sprint Burndown gadget can help a Scrum team review remaining work during an active sprint.

Jira editions, project configuration, permissions, and gadget availability can vary. Check what your team’s Jira environment supports before designing a dashboard around a specific gadget.

Choose gadgets around the team’s decisions

Start with a question, then choose the gadget that helps answer it. This simple approach keeps the dashboard tied to team decisions instead of turning gadget selection into a browsing exercise.

Here’s why: different roles need different views. Developers may need to spot blockers, while a delivery lead may want to compare completed work with incoming requests.

Match common questions to useful views

“What needs attention today?” Use a Filter Results gadget with a saved filter for open blockers or overdue issues.
“How is the sprint progressing?” Consider a Sprint Burndown or other sprint-focused gadget available in your Jira setup.
“What types of issues are in the queue?” A Pie Chart or statistics gadget can summarize issues by priority, status, or another relevant field.
“Are resolved issues keeping pace with new ones?” A Created vs. Resolved Chart can help show how work is entering and leaving the queue over time.
“Where is the work concentrated?” A Two Dimensional Filter Statistics gadget can compare two fields, such as assignee and status.

For example, an Agile team with recurring production blockers could display a filtered list of unresolved high-priority issues. That view makes urgent work easier to spot than a broad chart showing every issue in the project.

Use a chart when the shape of a trend matters. Choose a list when someone needs to act on specific issues.

Build a dashboard step by step

A practical dashboard usually starts with a clear purpose, a suitable saved filter, and a small number of gadgets. Build the first version for one audience, then adjust it after the team has used it in real work.

Choose the audience. Decide whether the dashboard is for a delivery team, a Scrum team, project leads, or a wider group.
Write down the questions. Pick three to five questions the dashboard should help answer, such as whether blockers are growing or sprint work is on track.
Prepare saved filters. Create focused Jira searches for the issues each gadget should display. Check filter sharing so intended viewers can see the results.
Create or select a dashboard. Use Jira’s dashboard controls to create a new dashboard or update one you’re allowed to edit.
Add and configure gadgets. Select only the panels that serve the questions you identified. Set each gadget to use the right project, saved filter, time range, or field.
Arrange the layout. Place urgent, frequently checked information near the top. Group related trends together so people can scan the page without jumping between unrelated panels.
Test with the intended audience. Ask a teammate to open the dashboard and explain what they would do after seeing it. Fix unclear labels, missing permissions, or irrelevant results.

Let me explain with a small example. A six-person Scrum team could begin with a sprint progress gadget, a list of active blockers, and a chart of open issues by priority. That’s enough to support a stand-up without overwhelming the page.

Dashboard and filter permissions matter. If a gadget appears empty for a teammate, confirm they can access the project and the saved filter it relies on.

Understand the gadgets Agile teams often use

Gadget names and availability can differ by Jira edition and setup, so treat this as a shortlist to verify in your own environment. Focus on what each view helps the team notice, rather than adding every option that appears relevant.

Issue lists and saved-filter results

A Filter Results gadget displays a selected set of issues. It works well for actionable lists, such as unresolved blockers, issues assigned to a release, or high-priority work with no assignee.

Keep the list narrow. If a team has to scroll through hundreds of issues to find the few that need attention, the filter needs refinement.

Charts and issue statistics

A Pie Chart can give a quick breakdown by a field such as priority or status. Two Dimensional Filter Statistics can compare two fields, which may help reveal where work is accumulating.

These gadgets summarize patterns, but they don’t explain every cause. If a chart shows a large number of issues assigned to one person, review the actual work and context before deciding that the workload is unbalanced.

Sprint and delivery progress

Sprint-focused gadgets can help teams inspect remaining work or understand how a sprint is progressing. A burndown view, for example, can make changes in remaining work easier to discuss during a review.

Pair a trend with a direct view of the work when people need to investigate. A progress chart shows a pattern; a filtered issue list can help the team find the items behind it.

Activity and team-specific panels

Some teams benefit from activity-focused views or gadgets that surface recent changes. These can be helpful when a project changes quickly, but they may become distracting if they show activity with no clear connection to team decisions.

Start with a short trial. If a panel rarely prompts a question or action, remove it and use the space for something more useful.

Use an example layout, then keep it current

Think of the dashboard as a team’s working view, not a permanent report. A Scrum team might use a simple two-column layout that puts immediate work first and broader trends second.

Example: a Scrum team dashboard

Top left: Sprint progress, so the team can see how the current sprint is moving.
Top right: A Filter Results gadget listing open blockers and their owners.
Lower left: A priority breakdown of open issues, useful for spotting shifts in the backlog.
Lower right: A created-versus-resolved trend, if the team also needs to monitor incoming work over time.

The team can check the top row during a daily stand-up, then use the lower charts during a weekly planning discussion. If the chart doesn’t help answer a recurring question, replace it with a more relevant view.

The best part? You don’t need to get the layout perfect on the first try. Ask teammates which panel they use, what they ignore, and what information they still have to search for.

Review the dashboard as work changes

Filters can become stale as teams change projects, workflows, issue types, or field conventions. Set a recurring review, perhaps once per sprint, to check that gadgets still display relevant results.

Watch for empty panels, duplicated information, and charts that combine unlike work. A dashboard showing completed work from several unrelated projects may look comprehensive while obscuring the status of each team.

A More Connected Project Workspace: ONES.com

When Jira dashboards are part of a wider effort to coordinate project work and team knowledge, ONES.com offers a unified platform for project management and knowledge management. Its separate products, ONES Project and ONES Wiki, can support delivery work and shared team knowledge in one platform.

ONES.com product screenshot

Core capabilities

Scattered project and reference information → ONES.com brings project management and knowledge management together, helping teams connect active work with relevant team knowledge.
Teams need Jira-style workflows → ONES Project supports Jira-compatible workflows, so teams can work with familiar process patterns while managing projects in ONES.
Limited visibility into progress → Built-in reporting gives teams project views without relying on a growing collection of add-ons.
Different work needs different processes → Custom workflows and fields let teams shape issue handling around their work.
Sprint planning feels disconnected from daily work → Sprint management helps Agile teams organize and track sprint activity within the project workspace.
Repeated project actions take time → Automation can handle selected workflow tasks, helping teams reduce repetitive manual steps.
Teams need a knowledge base alongside project work → ONES Wiki provides knowledge management as a Confluence alternative, sold separately from ONES Project.
Deployment requirements vary → ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions.

ONES Project is a project management product and a Jira alternative. Its workflow and project capabilities can be relevant to teams reviewing how they manage Agile work, while built-in reporting and automation may reduce reliance on additional plugins.

Application scenarios

An Agile team reviewing its project setup: A team that depends on Jira-compatible workflows can assess ONES Project for sprint management, custom fields, and reporting. The team can compare how its existing processes fit before planning a transition.

A distributed organization connecting delivery and team knowledge: A group can use ONES Project for project management and ONES Wiki for knowledge management. Because the products are sold separately, the organization can consider each product according to its needs.

ONES.com offers a free plan for up to 30 seats. Teams can evaluate its deployment options and product fit against their technical requirements, particularly when self-hosting or air-gapped operation matters.

Common challenges with Jira dashboards

Gadgets show empty results

Problem: A gadget appears blank for a teammate even though it works for its owner. Solution: Check access to the project, saved filter, dashboard, and any fields used in the gadget configuration.

The dashboard feels crowded

Problem: People must scan many panels to find the information they need. Solution: Remove gadgets that repeat other views or fail to support a recurring decision. Keep urgent and actionable information easy to find.

Charts seem to contradict each other

Problem: Two gadgets show different totals, leading the team to question the dashboard. Solution: Compare their saved filters, time ranges, issue types, and status rules. Differences in configuration can produce different counts.

Numbers lack useful context

Problem: A chart shows a sudden change, but nobody knows what caused it. Solution: Pair the trend with a filtered issue list or review the relevant work in Jira. Treat the chart as a prompt for investigation, not a complete explanation.

FAQs

What are Jira dashboard gadgets?

Jira dashboard gadgets are panels that display project information, issue lists, charts, or Agile progress. You can add and configure gadgets to help a particular audience answer practical questions. For example, a saved-filter gadget can list open blockers, while a sprint-focused gadget can help a team review work in progress. Availability and configuration can vary across Jira environments.

Which gadgets should an Agile team start with?

Start with a few views connected to recurring team decisions. A Scrum team might use a sprint progress gadget, a focused list of blockers, and a chart showing open issues by priority. A team monitoring work intake may also find a Created vs. Resolved Chart useful. Check which gadgets are available in your Jira setup, then remove any panel that doesn’t help the team act or investigate.

Why can a Jira gadget appear empty?

A gadget may appear empty because its saved filter returns no matching issues, or because the viewer lacks access to the project or filter. Configuration choices can also narrow results more than intended. Check the filter directly, review its sharing permissions, and confirm the gadget uses the expected project, time range, and fields. Ask another teammate to test the dashboard after you make changes.

How many gadgets should I put on one dashboard?

There’s no fixed number that suits every team. Start with a small set that answers the dashboard’s main questions, then add a panel only when it fills a clear gap. A compact dashboard with four useful gadgets is often easier to scan than one with many overlapping charts. Review usage with the people who rely on it, and remove panels that rarely influence discussion or action.

Conclusion

A useful Jira dashboard begins with the team’s questions, then matches each question to a clear gadget. Saved filters, access permissions, and a readable layout matter just as much as the charts themselves.

Start small: build a focused view, test it with the people who will use it, and review it as the work changes. That approach turns dashboard panels into practical signals, helping Agile teams spot blockers, discuss progress, and decide what deserves attention next.