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

Items from multiple project types in oneboard.

Robert Achmann

Ok, we all know how we can view multiple project items into a single board... change the board filter to have 'Project IN (PROJCODE1, PROJCODE2,etc, etc)'

But if the project types are not similar (KANBAN for one project and Scrum for the other) then I can't see the KANBAN 'tasks' in the Scrum project. I can only see the KANBAN epics.

Is there any way to view all items from both projects in one board, even though they are different project types?

Accepted answers

Bill Sheboy

Hi @Robert Achmann

What have you tried so far?

I am asking because I would think this would work as long as you treat the shared board as a read-only Kanban board and make no changes to the issues on it.

Maybe try this:

Create a Kanban board with a filter to span your desired projects
Create columns to roll-up the status values used for your Scrum and Kanban boards of those projects
And now the key part: map *all* of the status values from the other boards onto the columns of this board, ensuring the status categories are the same. So all of the "TO DO" go in the left column, all "COMPLETE" go in the right column, and all "IN PROGRESS" are distributed in your middle columns.
Do not transition any of the issues on this board, only on their source boards

Best regards,

Bill

All comments

Bill Sheboy

Hi @Robert Achmann

What have you tried so far?

I am asking because I would think this would work as long as you treat the shared board as a read-only Kanban board and make no changes to the issues on it.

Maybe try this:

Create a Kanban board with a filter to span your desired projects
Create columns to roll-up the status values used for your Scrum and Kanban boards of those projects
And now the key part: map *all* of the status values from the other boards onto the columns of this board, ensuring the status categories are the same. So all of the "TO DO" go in the left column, all "COMPLETE" go in the right column, and all "IN PROGRESS" are distributed in your middle columns.
Do not transition any of the issues on this board, only on their source boards

Best regards,

Bill

Robert Achmann

Thanks. After playing with it for a bit, I think the visibility issue is that project 1 (Or its user base) doesn’t have access to the workflow from project 2. If I assign P2’s workflow to P1, then P1 users see nothing at all in P1

Bill Sheboy

Hi...

A board is a view of issues using a filter, which can include one or many projects.

A workflow indicates the possible status paths for an issue type.

So, as long as one board (for multiple projects) maps all included status values in the workflows, it should be okay. There should be no need to change the original project's workflows.

What is the desired visibility of the new board: is it for people using both projects or something else?

Robert Achmann

I understand all of the differences which is why this issue surprised me in the first place. As long as both boards sort out what statuses show up in which columns on the board, it shouldn’t matter. All statuses from each workflow should be available to select which column they should live in. My issue though seems to be around the permissions. I’ll update when I have a clearer picture.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

board

query