How to Create a Jira Dashboard: A Step-by-Step Guide (2026)
Need a clearer view of Jira work? Learn how to create dashboard in Jira with useful gadgets and sharing settings. Read now to get started.
A Jira project can generate plenty of useful activity, yet the details you need may be scattered across issue lists and reports. When a deadline moves or blockers pile up, finding the right view can take longer than acting on what it shows.
A dashboard brings selected project information together, but a cluttered layout can create more noise than clarity. Sharing it also takes care: people may see the dashboard but lack permission to view its filters or projects.
Here’s the good news: you can create a focused Jira dashboard by choosing a clear purpose, adding a few relevant gadgets, and checking access before you share it. I’ll walk you through each step, explain which gadgets fit common needs, and show you how to keep the dashboard useful over time.
How to Create a Dashboard in Jira
To create a Jira dashboard, open the dashboard directory, create a dashboard, set its access, and add gadgets that display useful project information. Then arrange the layout and check that intended viewers can see the dashboard and its underlying content.
Here’s why the order matters: dashboard visibility and permission to view the issues behind a gadget are separate things. Use these steps to build a dashboard that is both useful and accessible.
-
Decide what the dashboard needs to answer. Pick a specific purpose before adding gadgets. For example, a team lead may need to see active work, overdue issues, and sprint progress in one place.
Keep the intended audience in mind, too. A personal planning view can include details that would overwhelm an executive summary.
-
Open the dashboard directory. In Jira, open Dashboards from the main navigation, then choose the option to view or manage dashboards. Select Create dashboard.
Jira’s navigation can vary by product version and configuration. If you don’t see the option immediately, look for the dashboard directory in the navigation menu.
-
Name the dashboard and choose its starting point. Use a name that explains its purpose, such as “Product Team Sprint Overview.” Add a short description if it will help colleagues understand what the dashboard shows.
You may be able to start with a blank dashboard or copy an existing one. A blank dashboard gives you a clean layout; a copy can save time when you already have a suitable model.
-
Set sharing and access permissions. Choose who can view or edit the dashboard using the available sharing options. Keep access limited to the people who need the view, especially when it includes sensitive project details.
Dashboard permissions do not automatically grant permission to view every project or saved filter shown on it. Check the access settings for those items separately.
-
Add gadgets that serve the dashboard’s purpose. Select Add gadget, browse the available gadgets, and add the ones that answer your chosen questions. Common examples include Filter Results, Pie Chart, and Created vs. Resolved.
Some gadgets need a saved filter or other configuration before they can display useful information. If you need a filtered issue list, create and save a suitable search first.
-
Configure each gadget and arrange the page. Open a gadget’s settings and select the project, filter, or other options it needs. Give it a clear title, then place it where viewers will find it easily.
Put the most important information near the top. A compact first row with current sprint work and blockers is often more useful than a long page of charts.
-
Check the dashboard as a viewer. Review every gadget for useful results, clear labels, and sensible time ranges. If possible, ask someone with the intended access level to open the dashboard and check what they can see.
Look for empty gadgets, missing filter permissions, or issue details that appear unavailable. Make any needed access changes, then confirm the dashboard works for its audience.

Plan the Dashboard Around a Real Question
A dashboard works best when it helps someone make a decision. “Which issues are blocking this sprint?” is more useful than “What charts can I add?” Start with one main question, then choose only the information needed to answer it.
For example, a project manager tracking delivery might need a list of overdue issues, a view of work by status, and a sprint progress gadget. A leadership view may need fewer details, such as open work and recent delivery trends.
The best part? You can create separate dashboards for different audiences instead of trying to make one page serve everyone. Keep each one focused, and viewers are less likely to overlook the information that matters.
Choose Gadgets That Make Information Easier to Act On
Gadgets turn Jira information into lists, charts, and summaries. Choose them for a clear reason: a Filter Results gadget can highlight issues needing attention, while a Pie Chart can show how issues are distributed across a selected field.
For a team reviewing delivery, Created vs. Resolved can help show whether incoming issues are outpacing completed ones. A sprint-related gadget can help a team follow progress during an active sprint, depending on the Jira product and gadgets available.
Let me explain: more gadgets do not automatically create a better overview. If your team adds six charts showing similar status counts, viewers have to work harder to find the next action. Start small, then add a gadget when you can name the question it answers.
Set Up Filters and Sharing Carefully
Many gadgets rely on saved filters to decide which issues appear. Create a filter with the right project, status, assignee, or date range, then save it with a name that explains its purpose.
When a colleague sees an empty gadget, the dashboard itself may still be shared correctly. The saved filter may not be shared with them, or they may not have permission to view the project’s issues.
Check dashboard access, filter access, and project permissions as separate settings. For instance, a team can have permission to open “Sprint Overview” while lacking access to the filter that powers its overdue-issues list.
Maintain a Dashboard That Stays Useful
Project priorities change, so review the dashboard when teams, workflows, or reporting needs change. Remove gadgets that no longer guide a decision, and update filters when their criteria stop matching the work.
A monthly check can catch common problems. Confirm that gadgets still show results, titles remain understandable, and the intended audience still has access.
You might be wondering: should you keep a dashboard if nobody checks it? Ask its audience what they use, then adjust or retire parts that no longer help. A smaller, current view is easier to trust than a crowded page that has gone stale.
Project Reporting Solution: ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.

For teams reviewing Jira dashboards, ONES Project may be worth considering when project reporting, workflow configuration, or deployment requirements are part of a broader project management decision. Its reporting and planning capabilities help teams bring project oversight into a single environment.
Core Capabilities
- Scattered project oversight → Built-in reporting → Review project progress through reporting capabilities without relying on a collection of separate add-ons.
- Workflows that don’t match team processes → Custom workflows and fields → Adapt issue tracking to the team’s process and capture details that matter to its work.
- Unclear sprint progress → Sprint management → Organize sprint work and follow delivery activity within the project management workflow.
- Repeated manual actions → Automation → Reduce routine work by automating suitable project processes.
- Concern about moving from Jira → Jira-compatible workflows → Make it easier to carry familiar workflow patterns into a Jira alternative.
- Too many separate plugins → Native feature parity across cloud and self-hosted versions → Keep core capabilities available without depending on as many add-ons.
- Strict hosting or network requirements → Cloud, On-Premise, Private Cloud, and Air-gapped deployments → Choose a deployment that fits the organization’s infrastructure needs.
ONES.com offers a free plan for up to 30 seats. Its four deployment options are Cloud, On-Premise, Private Cloud, and Air-gapped, with full feature parity between cloud and self-hosted versions.
Application Scenarios
A team seeking a Jira alternative: A product team can assess ONES Project when it wants project management with Jira-compatible workflows, sprint management, custom fields, automation, and built-in reporting.
A team with self-hosting requirements: An organization that cannot use a public cloud deployment can evaluate On-Premise, Private Cloud, or Air-gapped options while considering the same core feature set.
ONES Project is a separate product from ONES Wiki. If a team also needs knowledge management, it can assess ONES Wiki separately rather than assuming it is bundled with ONES Project.
Common Dashboard Challenges
- The dashboard is crowded. Too many gadgets make it harder to spot urgent work. Remove duplicate views and keep only gadgets that answer a specific question.
- A gadget shows no issues. Check its configuration, saved filter criteria, filter sharing, and project permissions. A narrow date range or an incorrect status condition can also return no results.
- Colleagues cannot open the dashboard. Review the dashboard’s sharing settings and confirm the person or group has the intended permission.
- Colleagues can open it but see incomplete results. Check access to the saved filters and projects behind the gadgets. A visible dashboard does not override permissions on its contents.
- The dashboard becomes outdated. Schedule a regular review and update gadget settings when the team’s workflow, reporting needs, or project structure changes.
FAQs
Can I create more than one Jira dashboard?
Yes. You can create separate dashboards for different projects, teams, or reporting needs, subject to your Jira permissions and product configuration. For example, you might maintain a sprint dashboard for developers and a higher-level delivery view for project leads. Give each dashboard a clear name and audience so people can choose the right view quickly.
What is the difference between a Jira dashboard and a saved filter?
A dashboard is a page that can display one or more gadgets. A saved filter defines which issues a search returns, and gadgets can use that filter to show a list or summary. You can use a dashboard without a saved filter, but many issue-focused gadgets need one. Check filter sharing and project permissions when other people need to see its results.
Why can someone see my dashboard but not its gadgets?
Dashboard access and access to the information inside it are separate. A person might be able to open the dashboard but lack permission to view a saved filter or the project issues that filter returns. Check the gadget’s settings, filter sharing, and project permissions. If the person still sees an empty view, review the search criteria and date range.
Which gadgets should I add first?
Start with gadgets that answer the dashboard’s main question. For a sprint overview, you might add a relevant issue list and a sprint progress view. For a delivery overview, a created-versus-resolved chart or a status summary may be more suitable. Available gadgets can vary by Jira configuration, so choose from what your instance provides and avoid adding duplicate views.
Can I make a Jira dashboard private?
Jira provides dashboard sharing controls, but the exact options can depend on your permissions and configuration. When creating or editing a dashboard, review its sharing settings and restrict access to the intended people or groups. Also check saved filters and project permissions separately, since private dashboard access alone does not control who can view every underlying issue.
Conclusion
A useful Jira dashboard begins with one clear question, not a long list of gadgets. Create the dashboard, set sharing, add a few relevant views, and check both gadget configuration and access to the information behind it.
When the dashboard feels crowded or shows incomplete results, simplify the layout and review permissions before adding more. That small maintenance habit can help you keep the view reliable as project needs change.
If your reporting needs connect to a broader project management decision, ONES Project is one Jira alternative to assess. Choose the approach that helps your team see the work clearly and act on it with confidence.