-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
6.3.13.0
-
6.03
-
6
-
Severity 3 - Minor
-
0
-
Problem Definition
When using Epics as a Swimlane, if the Epics are from a different project (one that is not covered in the filter of the board), any tasks under that Epic will not show up in the board, even if the task rightfully belong to that board. For example :
- Given Project A and Project B
- Project A has a Rapid board with a filter that only shows issues in Project A
- Project B has an Epic, called Epic B
- Task A from Project A is linked to Epic B via Epic Link
- In the Rapid board, the swimlanes are configured to be based on Epics
- Even though Task A shows up in the board (in the backlog), it does not show in the Sprint due to the Swimlane settings (and due Epic B being from another project)
Suggested Solution
Although it has been explained in GHS-7286 that it is an expected behavior that the Epic tag is missing in the backlog, it gets more complex in this case as the Task itself is not showing up in the board at all. This should be handled better, perhaps by adding a section called 'External Epics' when viewing the Sprint.
Alternatively, this can be avoided if the 'Epic Link' field is limited to only show Epics from the selected project, as per - GHS-12016
Workaround
For now, the only workaround would be to not configure Epics as the Swimlane
- is related to
-
-
- Closed
-
- relates to
-
JSWSERVER-12016 The "Epic Link" field list Epics from all the projects instead of the current one
- Closed
-
- Gathering Interest
[JSWSERVER-12025] As a user I want tasks linked to external Epics to show up in the Epic Swimlane so I can work on them
Kent Mingus
added a comment - Many of our departments use the Kanban board with epics for swimlanes to queue and track progress of work. Now that we understand this bug, we find that many of us have been missing tasks that should have been worked on for some time. This is a serious issue for us and one that makes kanban boards virtually unusable.
Kent Mingus
added a comment - Many of our departments use the Kanban board with epics for swimlanes to queue and track progress of work. Now that we understand this bug, we find that many of us have been missing tasks that should have been worked on for some time. This is a serious issue for us and one that makes kanban boards virtually unusable. That is not a suggestion but a bug.
Please refer to my original ticket https://jira.atlassian.com/browse/GHS-11999
Simply saying, using external epics and the generate swim-lanes using epic its not possible to access those tasks. That's a serious limitation\problem to the generate swim-lanes functionality as it becomes unusable.
This is more complex problem and related to https://jira.atlassian.com/browse/GHS-7286.
And its highly depended on the https://jira.atlassian.com/browse/GHS-12016.
If Epic list will be limited to the project only, it won't be possible to link an external epic and there won't be a problem with the swim-lanes creation. The resolution of GHS-12016. will have a huge impact on our jira project\portfolio structure.
This looks to be a duplicate of https://jira.atlassian.com/browse/JSWSERVER-11318. We agree this is a bug.
Note also the possible workaround listed from Ert Dredge from that other bug if you have ScriptRunner or similar.