-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Problem
When using Base Swimlanes by Epics on a Kanban board, if the issue belong to the filter but its parent Epic does not, the issue will not be displayed as the Swimlane will not be shown for it.
I could also reproduce this behavior with the following information:
- Created a fresh Kanban board with the following JQL filter:
- assignee in (testuser)
- Created two epics:
- EPIC A: assigned it to "adminuser"
- Created an an issue "Test Issue One" inside EPIC A and assigned it to "adminuser"
- EPIC A: assigned it to "adminuser"
-
- EPIC B: kept unnassigned
- Created an an issue "Test Issue Two" inside EPIC A and assigned it to "adminuser"
- EPIC B: kept unnassigned
When the board is using "Base Swimlanes by Queries":
- EPIC A: displayed
- Test Issue One: displayed
- EPIC B: not displayed (doesn't have an assignee from the filter)
- Test Issue Two: displayed
When the board is using "Base Swimlanes by Epics"
- EPIC A: has a swimlane for it
- Test Issue One: displayed under EPIC A's swimlane
- EPIC B: does not show a swimlane for it (doesn't meet filter conditions)
- Test Issue Two: not displayed
Suggested Solution
Add a condition to allow Epics from outside the filter to be displayed if it has issues from the filter.
Why This Is Important
This allow more control and visibility when the Epic doesn't meet the criteria of the board but its issues belong to it.
Workaround
You may either:
(1) Use other Swimlane formats,
(2) Edit the filter conditions to include the Epic.