Is it possible to show/hide Kanban Board status column(s)?

John Tucci

We are running team-managed Kanban boards, and we want to expand our primary project to include another team (QA/Test). We have their workflow defined so that I can add that to our established project Workflow. However, doing so would six more columns/statuses to our board, making it extremely wide.

It would be a significant help if users could selectively show/hide columns so they could focus on their portion of the overall Workflow.

Is there a way to create separate projects for each team while linking the boards so that issues could move across project boundaries? 

Trudy P Claspill

Hello @John Tucci 

TMPs don't provide a method for selectively hiding columns.

Team Managed projects are meant to be entirely independent. The agile boards created for a TMP has functionality that is unique to TMP. If you are familiar with separately creating agile boards from saved filters for Company Managed projects, you can technically do this for a TMP but the board functionality is different and you will encounter some problems if you try to go that route. Let me know if you want more details on that.

So, creating separate TMP projects for each team and linking boards also is not an option.

You could do this with one Company Managed project and two boards, but you might want to review the discussion I've been having with another user in this other post on that same topic.

https://community.atlassian.com/t5/Jira-Software-questions/When-opening-a-new-sprint-all-tickets-in-1-column-on-our-second/qaq-p/1839901

You could set up two Company Managed projects, but then you would have to have separate stories for the QA/Test team, generated from and linked to the primary team's stories. With two Company Managed projects each team could have their own board and their own workflow, and you could also create a board that showed the issues from both teams.