Hide one of the status on Jira Board for a Team-managed project
Hello,
I have a team-managed project and I want to hide the Backlog section on the board so that the board looks less complicated. How do I do this? Please help.
Attaching the view of my current board.
3 answers
There should be a place where you can configure board settings.
In the left-hand menu, under the Project Board section, if you click the "..." (more options), is there a settings menu?
For a Business project the options for board configuration are limited.
From Project Settings these are the available options. As you can see, there is not Board option.
And these are the only options available from the board view itself.
The settings you are thinking of are available only for boards created with Software projects, or boards created from Saved Filters.
Thank you for that additional information.
Based on the image you provided you are using a Team mananaged business project.
With such a project you board configuration options are limited.
There is not an option for a "Backlog" screen to which you can relegate the backlog items so that they don't disrupt the focus of the board view. A Backlog screen option is available in the boards used with Software projects.
You cannot remove the Backlog column from the board in these projects. The column is directly tied to the Status it displays. Removing the column means deleting the status from the workflow. In that case the issues have to be assigned to another status, so that does not solve your problem.
With a Team Managed Business project your only options are to collaps the column as suggested by @Valerie Knapp or use a filter to hide the issues.
You could consider setting up a separate project specifically to hold your Backlog issues. Moving the issues to that other project would hide them from this board. Your team would need to review the backlog in that other project. As items near the point at which they could become actionable, you could move them back into this project. That would reduce the number of issues shown in the Backlog of this project.
You could consider create a Software project, and moving all the issues to that project. With a Software project you can elect to use a Kanban board and enable a Backlog screen. The "backlog" issues are then displayed on the Backlog screen, reducing the number of issues visible on the board.
With a Team Managed Software project Kanban board you would still have a column for every status. Visibility of an issue in the columns of the Boards is determined by its presence in the Board list vs. the Backlog list on the Backlog screen.
With a Company Managed Software project Kanban board the visibility of an issue on the board is based on its Status. You decide which Statuses mean an issue is "in the backlog". Columns for those statuses are not shown on the board. To show an issue on the board you changes its status.
Moving issues to another project is something that should be carefully planned and tested in the small scale before making the decision to move all the issues. Links between parent Epics and child issues may be broken. If there is a mismatch in the available fields data loss may occur.
@Trudy Claspill I have the capability of changing the project category to 'Software'. Is it the same option you are referred in your last comment "You could consider create a Software project, and moving all the issues to that project. With a Software project you can elect to use a Kanban board and enable a Backlog screen. The "backlog" issues are then displayed on the Backlog screen, reducing the number of issues visible on the board.".
If so, and after I change the category to 'Software'
1. Can you confirm if this will not impact any other sections?
2. can you guide me with the next steps (which you explained above) so that I can have the capability to remove the 'Backlog' field from Kanban board without actually removing this field from the entire workflow.
Hello @HQRAZAHS
I have the capability of changing the project category to 'Software'. Is it the same option you are referred in your last comment "You could consider create a Software project, and moving all the issues to that project.
No, that is not what I was referencing. The project Category and the project Type are not the same thing. Changing the Category to Software will not change the underlying architecture of the project.
You would need to create an entirely new and separate Project using the Software Development > Kanban template.
1. Can you confirm if this will not impact any other sections?
Since this is an entirely new and separate project, none of the "sections" in your original project would be applicable anymore.
2. can you guide me with the next steps (which you explained above) so that I can have the capability to remove the 'Backlog' field from Kanban board without actually removing this field from the entire workflow.
If you are not a Jira Administrator, your only option will be to create a Team Managed Software project. In that case be advised that this functionality would apply:
With a Team Managed Software project Kanban board you would still have a column for every status. Visibility of an issue in the columns of the Boards is determined by its presence in the Board list vs. the Backlog list on the Backlog screen.
To make an item visible on the board, in the Backlog screen you drag the item from the Backlog section of the list up to the Board section of the list. To remove an item from the board view you reverse that.
However, before getting to that point there are other steps you would need to take, including but not limited to:
- Configuring the workflow in your new project to match the workflow in the original project
- potentially creating new issues types in the new project to match the issue types in the original project
- potentially creating new Custom Fields in the new project to match any custom fields you had created in your original projects
After getting the new project configuration set to match your original project, you would have to use the Move Issue function to move all the issues from the original Business project to the new Software project.
I strongly recommend you test that on a small scale by setting up some test issues in your original project and trying to move them to your new destination project. Do that before trying to move any of your issues that track real work, as unanticipated problems and/or data loss might occur during the move.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.