Create a Jira Dashboard: A Step-by-Step Guide for Teams
Need a clearer view of team work? Learn how to create a Jira dashboard with useful gadgets, filters, and sharing settings. Read now to get started.
A Jira dashboard can turn scattered project activity into a clear view of what needs attention. But setting one up can feel confusing when you face dozens of gadgets, filters, and sharing options.
A cluttered dashboard can hide overdue work, bury sprint risks, and show teammates information they cannot access. Even a polished layout becomes frustrating if its charts rely on the wrong filters.
Here’s the truth: you can build a useful dashboard by starting with a team question, choosing a small set of gadgets, and checking who can see them. I’ll walk you through each step, from creating your dashboard to keeping it useful as your project changes.
You’ll also see how to tailor the layout for different roles and troubleshoot common visibility issues. The goal is a practical view your team can act on, not a wall of charts.
How to Create a Jira Dashboard Step by Step
Start by deciding what your team needs to know at a glance. Then create the dashboard, add only relevant gadgets, and test the result with the people who will use it.
- Choose the dashboard’s purpose. Write down one or two questions it should answer. A sprint team might ask, “What is unfinished?” and “Which issues are blocked?” A support team might focus on incoming requests and overdue work.
- Create a new dashboard. In Jira, open Dashboards and choose the option to create a dashboard. Give it a clear name, such as “Mobile App Sprint Overview.” Depending on your Jira version and permissions, you may be able to start from a blank dashboard or copy an existing one.
- Set access and sharing. Choose who should be able to view or edit the dashboard. Keep it private while you build and test it. When you are ready, share it with the appropriate people or groups, using the permissions available in your Jira setup.
- Add the gadgets your team needs. Select the dashboard option to add gadgets. Common choices include a filter results list, a pie chart, a two-dimensional filter statistics gadget, and sprint-related gadgets. Availability can vary by Jira version and configuration.
- Configure each gadget. Select a saved filter, choose the fields or statistics to display, and adjust the number of results. For example, a filter results gadget could show unresolved issues assigned to your team, with columns for priority, status, and assignee.
- Arrange the layout. Move gadgets into columns and place the most useful information near the top. Put an urgent work queue before a broad chart so teammates can spot action items quickly.
- Test the dashboard with a teammate. Ask someone with the intended access to open it. Confirm that the gadgets load, the filters show the right issues, and the labels make sense without an explanation.
Let me explain: gadgets display information through filters and configuration, so a dashboard is only as useful as the rules behind it. If a chart looks empty, check its filter and permissions before adding more gadgets.

Plan the Layout Around Team Decisions
A dashboard works best when its layout reflects the decisions your team makes during the day. Start with the most time-sensitive question, then place supporting context below it.
For example, a team lead may need to see blocked issues first, then work by status, and finally the sprint’s overall progress. A developer may prefer assigned work and recently updated issues at the top.
Give each dashboard a clear audience
One dashboard rarely serves every role equally well. A shared team dashboard can show sprint health, while a separate personal dashboard can focus on work assigned to one person.
Keep the audience specific in the name. “Platform Team: Current Sprint” tells teammates more than “Project Dashboard,” especially when several dashboards appear in the menu.
Keep the first screen actionable
Put information that triggers a next step near the top. An overdue issue list is actionable; a broad count of all completed issues may be useful lower down.
The best part? You can often improve a crowded dashboard simply by removing gadgets nobody uses. A focused set of four or five views is easier to scan than a page full of competing charts.
Choose Gadgets That Answer Real Questions
Each gadget should answer a question your team asks repeatedly. Before adding one, name the decision it supports and identify the filter or project scope it needs.
A filter results gadget can help a team review open issues assigned to its members. A pie chart can show how work is divided by status, while a two-dimensional statistics view can compare status and priority.
Match the gadget to the question
If teammates ask, “What should I work on next?” show a short list of issues filtered by assignee, priority, or due date. If a project manager asks, “Where is work getting stuck?” compare issue counts across statuses.
For sprint planning, use sprint-focused views available in your Jira setup. Check that the sprint is active and that the gadget points to the intended project or board.
Use saved filters carefully
Many gadgets depend on saved filters. Give each filter a descriptive name, and check that it returns the intended issues before connecting it to a gadget.
Filter access matters too. A teammate may see an empty gadget if they cannot view the filter or the underlying project issues. Test the dashboard using an account with typical team permissions.
Share, Review, and Maintain the Dashboard
Sharing settings determine who can open a dashboard, while project and filter permissions affect what its gadgets reveal. Review both layers before treating a dashboard as a team-wide view.
For example, a dashboard may be shared with a project group, but a gadget can still show no results if its saved filter is private. Check the dashboard’s sharing settings and the filter’s access separately.
Check the dashboard as a viewer
Ask a teammate to open the dashboard rather than relying only on your own view. They may see different results because their project access, filter permissions, or role differs from yours.
If your Jira setup allows a default dashboard, choose one that helps the intended audience begin their work. Explain where to find other role-specific dashboards so the default view does not become a catch-all.
Review gadgets as the project changes
Sprints end, teams shift, and saved filters become outdated. Review the dashboard at a regular planning or retrospective meeting, and remove gadgets that no longer guide a decision.
A simple review question helps: “What did we act on from this dashboard last week?” If the team cannot name an answer for a gadget, consider replacing it with a clearer view.
ONES.com Solution: Project Work and Team Knowledge Together
ONES.com brings project management and knowledge management together, so teams can coordinate work and keep useful guidance close to the project. ONES Project is the project management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

When teams are building dashboards and project routines, the challenge often extends beyond charts. People need consistent workflows, clear progress reporting, and a reliable place to capture decisions. ONES.com provides these capabilities across its platform, with ONES Project focused on planning and tracking work.
Core capabilities for project teams
- Workflows that match team processes: Teams frustrated by rigid issue flows can configure custom workflows in ONES Project, helping work move through the stages they actually use.
- Custom fields for useful context: When standard issue details leave gaps, teams can add custom fields and capture the information needed to plan or review work.
- Sprint management: Teams coordinating iterative work can manage sprints and track planned issues, making progress easier to review during a cycle.
- Built-in reporting: Teams that need routine progress visibility can use built-in reporting, reducing the need to assemble every update manually.
- Automation: Repetitive project actions can be automated, helping teams reduce routine handoffs and keep work moving.
- Jira-compatible workflows: Teams familiar with Jira workflows can use compatible ways of organizing work, supporting a more recognizable transition to a Jira alternative.
- Native feature parity across deployments: Organizations weighing cloud against self-hosting can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment while retaining feature parity between cloud and self-hosted versions.
- Fewer plugin dependencies: Teams that rely on multiple add-ons can use integrated project capabilities, which may reduce plugin dependence and simplify administration.
- Knowledge management through ONES Wiki: Teams that need project guidance alongside execution can use ONES Wiki as a separately sold knowledge management product.
Where teams may apply it
A product team can use ONES Project to manage sprint work, custom issue stages, and progress reporting. The team can keep recurring project guidance in ONES Wiki, so members have a clear place to refer to alongside their project activities.
An organization with restricted hosting requirements can consider On-Premise, Private Cloud, or Air-gapped deployment. A smaller team can begin with the free plan, which supports up to 30 seats, then assess its needs as work expands.
ONES.com is useful to consider when a team wants project management with Jira-compatible workflows, native deployment options, and fewer separate plugins. The right fit depends on your team’s processes, hosting needs, and access requirements.
Common Dashboard Challenges and Practical Fixes
- A gadget shows no results. Confirm that its saved filter returns issues, the project scope is correct, and viewers have access to both the filter and relevant issues.
- The dashboard feels crowded. Remove views that do not support a recurring decision. Put the most time-sensitive list first and move background information lower.
- Teammates see different results. Compare project access, filter permissions, and gadget configuration. Test the view with a teammate who has the access level you expect.
- A chart gives a misleading impression. Check the filter, chosen statistic, and reporting period. A chart can be technically correct while answering the wrong question.
- The dashboard becomes outdated. Add a brief review to sprint planning or retrospectives. Update filters and gadgets when team ownership, project scope, or workflow stages change.
Frequently Asked Questions
Can I create more than one Jira dashboard?
Yes, Jira can support multiple dashboards, subject to your permissions and setup. Separate dashboards can serve different purposes, such as sprint tracking, service work, or personal priorities. Give each one a distinct name and audience so teammates can choose the view that matches their work.
Why can a teammate see my dashboard but not its issues?
Dashboard access and issue access are separate considerations. The teammate may be able to open the dashboard but lack permission to view its saved filter or the project issues behind a gadget. Check the sharing settings for the dashboard and filter, then confirm the teammate’s project permissions.
Which gadgets should I add first?
Choose gadgets based on the questions your team needs to answer. A filter results list is a practical starting point for reviewing assigned or unresolved work. Add a chart or sprint view only when it gives the team useful context that the list cannot provide clearly.
Can I use a Jira dashboard for different team roles?
Yes. You can create separate dashboards for audiences with different needs, depending on your Jira permissions. A team lead might prioritize blockers and sprint health, while an individual contributor might focus on assigned issues. Use clear names and test access with someone in each intended audience.
Why does my dashboard look different from a teammate’s?
Differences can result from permissions, gadget settings, or changes in the saved filters being used. Some Jira versions and configurations also offer different gadget options. Compare the dashboard and filter access first, then check whether both people are viewing the same dashboard and project scope.
Conclusion
A useful Jira dashboard starts with a real team question. Create a focused view, connect gadgets to accurate filters, and check permissions from a teammate’s perspective.
Then keep the dashboard useful by reviewing it as your project changes. Remove clutter, adjust outdated filters, and make sure the top of the page points people toward their next action.
Dashboards can make project activity easier to understand, but only when their layout and access match the way your team works. Start small, test the view, and improve it with feedback.