Not seeing issues for added project on my multi-project board

[Ann Henson]

I successfully created a multi project board by first creating a filter for the first two projects and then creating a board using that filter.  It worked great and all the issues for those two projects showed up on my multi-project board.  However when I attempt to add a third project, the issues for the added project are not showing up on the board.  From the Configure Board page, I edited the filter to include the new project, and the search seems to be successful as both the existing and new projects show up on the Configure page.  However when you return to the Muti-project board only the issues from the original projects are displayed.

[Trudy Claspill · Accepted solution]

Hello @Ann Henson 

Welcome to the Atlassian community.

Are the projects Company Managed projects or Team Managed projects?

After adding the third project, did you go the the Board Configuration > Columns page and make sure the statuses used in the third project are mapped to columns of the board?

[Ann Henson]

Team Managed Kanban using the Kanban template.  Same columns for all projects

[Trudy Claspill]

Did you check the Columns and Statuses page for your multiple project board after updating the filter? You need to make sure that none of the Statuses are listed in the Unmapped Statuses section, but rather are mapped to columns of the board.

[Ann Henson]

By moving the unmapped issues to a column, the new project issues show up.  Is that going to happen every time I add a new project to this board?  Or is there something I should do different to keep that from happening?

[Trudy Claspill]

If you are adding Team Managed projects to the filter, yes, that will happen every time.

Team Managed project customizations are localized to each project. Even when the projects use identically named statuses, in the database each of those Statuses has a unique numeric ID. When you add another TM project to the filter it will not automatically map the statuses from the new project to the columns.

There is no work around for this when you are working with TM projects.

With Company Managed project the projects share globally defined status values, so if multiple projects use a Status named "Done", then they are all using the same one. In that case, when a new project is added to a filter, only the Status values used by the new project and not used by the projects already in the filter would end up in the Unmapped Statuses area.