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

Get data from multiple kanbans/projects

Jacob A. Albrektsen

Hi all

I am in a QA team atm. And we have divided our testing resources into release trains. I would like to have a shared Kanban, but would like to collect data from the release train Kanbans. example could be, if a QA tester is assigned to a task, in their release team, then it will automatically show up in QA team Kanban board.

Is this possible?
If so, how do I do this?

Accepted answers

Walter Buggenhout

Hi @Jacob A. Albrektsen,

That is not so difficult. You already mention several assignee filters. All you need to do is combine those into one single filter and then set that filter as the issue source of your QA Team kanban.

If you take a step back, that might become something mainly based on statuses:

Project IN (ProjectA, ProjectB, ProjectC ..., ProjectZ) AND
Status IN ("Ready for QA", "QA Review In Progress", "Accepted", "Need Improvement")

Statuses and projects are fictional, obviously. But I'm sure you get the point. Then, just map the relevant statuses to columns and you should be fine.

Baseline to remember: issues are only once in Jira, stored in projects. You can pull them in as many boards as you like or need, just by creating the appropriate filters for the purpose and then mapping statuses to columns.

Hope this helps!

All comments

Walter Buggenhout

Hi @Jacob A. Albrektsen,

That is not so difficult. You already mention several assignee filters. All you need to do is combine those into one single filter and then set that filter as the issue source of your QA Team kanban.

If you take a step back, that might become something mainly based on statuses:

Project IN (ProjectA, ProjectB, ProjectC ..., ProjectZ) AND
Status IN ("Ready for QA", "QA Review In Progress", "Accepted", "Need Improvement")

Statuses and projects are fictional, obviously. But I'm sure you get the point. Then, just map the relevant statuses to columns and you should be fine.