Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Built in Dashboards

alia.burale August 2, 2021

Is there a way to query cross-projects and view issues in a separate dashboards?

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 2, 2021

Hi @alia.burale 

What do you mean by "query cross-projects"?

A dashboard in Jira Cloud is a view of gadgets driven by a saved filter.  Some of the gadgets only need the project/board name.  If you can make a filter to list what you need, you may use it in a dashboard:

project IN (A, B, C) AND...

Please look here for more information about dashboards:

https://support.atlassian.com/jira-software-cloud/docs/create-and-edit-dashboards/

Best regards,
Bill

alia.burale August 3, 2021

Hi @Bill Sheboy

Thank you for your response. I'm researching the best practice to create a view in JIRA for POs  to view/track and manage issues across multiple projects. One way would be as you mention to create a  cross-projects filter and link it to a component or issue label. I'm wondering how could that be incorporated in a master dashboard that eventually could facilitate tracking issues from multiple projects.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 3, 2021

Thanks for clarifying, @alia.burale   I'm not certain there are any "best practices": perhaps only better and "worser" ones, as teams learn, experiment, and improve.  :^)

I noted dashboards, and there are also built-in Jira boards to use with multiple projects, roadmaps, and some calendar views.  If you look at the marketplace of addon products, there are many more options.

Please consider having a discussion with your product owners (PO), the team coaches, and your Jira site admin to learn what they want/need, what types of problems they are trying to solve, and what options the site admin describes as available.  For example, do the POs care about visibility, work coordination, risk management, scheduling, etc.?  Knowing those things will help improve on the correct problem/challenges.

One basic way to start is creating a simple Kanban board spanning multiple projects, treat it as read-only, and see how that helps.  I note treating it as read-only as you want the teams to update and manage their work rather than have a PO move issues the team is working upon.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events