nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is there a way to set up dashboards that work for everyone without overcomplicating things?

diceba8432

I’m struggling to create Jira dashboards that actually meet different stakeholders' needs.

Some want a big-picture overview, while others need detailed stats, and I feel like I’m constantly updating things to keep everyone happy.

Accepted answers

Sahir Maharaj_28wu8p

Hi @diceba8432

I totally get this and I agree with @Walter Buggenhout - different stakeholders have different priorities, and a one-size-fits-all dashboard rarely works.

What I’ve found effective is creating separate dashboards for different stakeholder groups rather than trying to cram everything into one.

The first action point I recommend is talking to stakeholders to understand what they actually need.

A project manager might want a high-level progress overview (issue trends, deadlines, etc..), while a developer might need detailed issue stats (assigned tasks, blockers, etc..).

Once you know what they care about, you can use Jira gadgets like Created vs. Resolved Charts, Issue Statistics, and Filter Results to display the right data.

To keep things streamlined, you can also create pre-set filters so that dashboards dynamically update without constant manual adjustments.

Here are some super valuable tutorials to get started:

Let me know if you have any questions - happy to help!

All comments

Walter Buggenhout

Hi @diceba8432 and welcome to the Community!

Different stakeholders having different needs / expectations is quite normal, to be honest. I am afraid that the ambition to build a "one size fits all" dashboard is not a realistic expectation nor possibility.

People run different projects and based on their role in the organisation simply need different types of information. Individual users may benefit of issue lists that display the work they are interested in across Jira (you can build a generic dashboard with list of issues where users are the assignee, reporter or watcher by using the JQL keyword currentUser() to dynamically display data for the logged in user). But a team lead, project lead or project manager will need higher level information about how the work is going for his/her domain. The source data will be different for every domain so you will need to adjust the data sources anyway and it is quite normal that different teams / projects face different challenges. So your reporting will need to be flexible to surface the information that matters most for each.

For project / team dashboards, you can create new dashboards from a sort of template, that contains gadgets that are valuable to most teams. But having to adjust them may require work, but is a valuable investment in the operations of your team(s).

Hope this helps!

Sahir Maharaj_28wu8p

Hi @diceba8432

I totally get this and I agree with @Walter Buggenhout - different stakeholders have different priorities, and a one-size-fits-all dashboard rarely works.

What I’ve found effective is creating separate dashboards for different stakeholder groups rather than trying to cram everything into one.

The first action point I recommend is talking to stakeholders to understand what they actually need.

A project manager might want a high-level progress overview (issue trends, deadlines, etc..), while a developer might need detailed issue stats (assigned tasks, blockers, etc..).

Once you know what they care about, you can use Jira gadgets like Created vs. Resolved Charts, Issue Statistics, and Filter Results to display the right data.

To keep things streamlined, you can also create pre-set filters so that dashboards dynamically update without constant manual adjustments.

Here are some super valuable tutorials to get started:

Let me know if you have any questions - happy to help!

Mary from Planyway

Hi @diceba8432

Sharing a recent article on Jira dashboards. Hope it'll be useful.

Marlene Kegel - codefortynine

Welcome to the community, @diceba8432.

I am Marlene, product manager of Quick Filters for Jira Dashboards.

A lot of Jira admins who work with our app gave us the feedback that they use our app to reduce the amount of dashboards on their instances.

Quick Filters for Jira Dashboards enable you to add a Quick Controller gadget on your Jira dashboard to filter all other Quick Gadgets on the dashboard dynamically.

This means you could create one dashboard which shows the big overview, and the add filters to the Controller Gadget to dynamically filter the displayed results to see some more details.

You could either filter per project, per assignee or team, per epic or sprint - and a lot more.

You can try out Quick Filters for Jira Dashboards without installing it on your own instance, on our demo dashboards.

I've also published an article about cross-project Jira Dashboards in the Atlassian Community that might be interesting for you.

quick-filters-jira-dashboards_controller_pie-chart_epic-link.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud