Forums

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

Items from multiple project types in oneboard.

Robert Achmann April 9, 2020

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?

1 answer

1 accepted

0 votes
Answer accepted
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.
April 9, 2020

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 April 9, 2020

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
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.
April 9, 2020

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 April 9, 2020

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. 

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.
April 9, 2020

One more thing to try regarding permissions: ask your system admin to try the permission helper to see if it can auto-magically diagnose what is happening.  Here's some info about it if you have not used it before.

https://confluence.atlassian.com/adminjiracloud/jira-admin-helper-818578850.html

Robert Achmann April 9, 2020

I am the site admin, so I’ll try that. The reason this surprised me was then when I first applied the workflow, I could see everything just fine but a normal user can’t. I guess I was in a rush and didn’t consider that difference of permissions and access. My bad. I’ll play with it

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.
April 9, 2020

Ah... It could also be related to permissions of the filters for the respective boards.  Have you checked that?

Robert Achmann April 9, 2020

Ah! Good one. I’ll check that

Robert Achmann April 14, 2020

It was both the filter permissions and assigning the other project's status' to the board columns.  Thanks

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events