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; } } }

How to include all projects by default on one kanban

Abby Foggin

I've set up a kanban to provide visibility of workload for certain users across all projects.

To do this, I had to click each individual project to include it, so each time we add a new project, it would need to be manually added.

Is it possible to include all projects in a kanban by default?

Would it likewise be possible to include all statuses by default?

My concern is this kanban is only useful if it includes all issues assigned to that team and will be a pain to maintain if people need to remember to add in new projects and statuses manually each time.

Accepted answers

Justina_kp5acv

Have you tired using advanced search in JQL? This looks like it may help you.

https://community.atlassian.com/t5/Jira-questions/JQL-Syntax-Query-How-to-select-all-Projects/qaq-p/2121269

The short version is, if you don't select a project, the search will pull issues from all projects. However, the user will only see issues from projects they have browse permissions to.

All comments

Justina_kp5acv

Have you tired using advanced search in JQL? This looks like it may help you.

https://community.atlassian.com/t5/Jira-questions/JQL-Syntax-Query-How-to-select-all-Projects/qaq-p/2121269

The short version is, if you don't select a project, the search will pull issues from all projects. However, the user will only see issues from projects they have browse permissions to.

Bill Sheboy

Hi @Abby Foggin -- Welcome to the Atlassian Community!

You may create a simple filter, only referencing those specific users of note, and then creating a board from that. For example:

assignee IN ("Alice", "Bob", "Grace") ORDER BY Rank ASC

For such a board, remember to always treat it as read-only, where any issue updates are only made by the teams on their source boards.

Even creating a board like this with no projects or issue types referenced in the filter will require adjustments as projects make changes. Otherwise changes to workflows and status mapping to the board will be incorrect.

One additional note: needing to create a board like this is often a symptom of a root cause, such as people capacity is low, too much WIP, etc. Please consider investigating that cause, or the visibility board could lead to unintended consequences (e.g., people decide not to assign work to themselves to avoid having the discussion).

Kind regards,
Bill

Abby Foggin

Thanks Justina- I'd come to the same conclusion so I can use JQL to exclude projects and alll others are therefore included by default.

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-software

jira-software-cloud