-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
2
-
As a product manager I to be able to hide the Everything Else Swimlane on board.
Background: I've built a board to view a subset of the work in flight for our group so our Director is able to report to the GM on specific, but evolving buckets of work. The board only displays Epics, and in our setup, Epics are children of Requirements.
I designed 3 swimlanes, one per concept, that contain 1:many requirement links as the determining factor if an Epic appears in the swimlane.
The problem is the Everything Else swimlane. The only way I have found to eliminate the Everything Else swimlane is to duplicate the JQL for the swimlanes in the filter criteria.
The result is every time there is a change in scope I will need to update both the Query and the Swimlanes, duplicating work.
I want the ability to hide/remove the Everything Else swimlane, and all of its contents, from view via the Board Configuration process.
This way I can send the same query and only need to update the swimlane JQL.
As 'Everything Else' is out of scope of the purpose of the board, displaying it just adds noise and the possibility of confusion by users.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-20019] Hide Everything Else Swimlane on a board
Please deprecate the "Everything Else" swimlane. Case: We have recently consolidated over 10 Jira projects into one, and our support team uses a filter based kanban board with filtered swimlanes; however, because of the immutability of the "Everything Else" swimlane, the board is not even able to be displayed because there are simply too many Jira issues on it.
This would be great, also a toggle to always show a swimlane.
If we add a filter that ends up with nothing in a swimlane, it removes the swimlanes and just floods the board with the issues we want hidden in Everything Else (In our case its not possible to hide unwanted Jiras without tagging every single Jira with a label to filter on).
Would be great. I don't see the help this swimlane might provide when you have a plethora of tickets to be just rendered (not read) there. Maybe for very small project it might make sense, but not in general, I would say