-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
1
-
Problem Definition
In example: When we use Swimlane based on a query that search for Epic Link, the issues are displayed correctly, however, the sub-tasks are not, they are displayed at the first swimlane of the list.
Steps to test the behavior:
- Create 3 Epics.
- Create issues with sub tasks and link the issues to the Epics.
- Base the Swimlanes on Queries.
- Use a query to search epics (i.e. "Epic Link" = 'EPIC-1' OR issuetype in subTaskIssueTypes()).
Suggested Solutions
By default, set to the sub-task the same Epic Link of its parent issue.
- duplicates
-
- Gathering Interest
- relates to
-
- Gathering Interest
[JRACLOUD-68909] Subtasks should inherit its parent Epic Link
Lukas van Driel (Q42)
added a comment - I'd also appreciate this feature.
I regularly have tasks on the backlog of which one or multiple subtasks are on the current kanban board. The kanban board has a swimming lane per epic, and these subtasks are then filed under "no epic attached". I would expect them to be filed under the epic of their parent task.
Lukas van Driel (Q42)
added a comment - I'd also appreciate this feature.
I regularly have tasks on the backlog of which one or multiple subtasks are on the current kanban board. The kanban board has a swimming lane per epic, and these subtasks are then filed under "no epic attached". I would expect them to be filed under the epic of their parent task. 
Alicja Skidmore
added a comment - As suggested by your support team, I'm voting on this issue and leaving you a comment to hopefully help prioritize this development.
Not having the ability to assign epic name to a sub-task deceives the object of smart planning. Currently our subtasks are visible in different swimlines than the parent one because we are unable to link them to its epic link.
Please add this feature as soon as possible to easy our planning.
Alicja Skidmore
added a comment - As suggested by your support team, I'm voting on this issue and leaving you a comment to hopefully help prioritize this development.
Not having the ability to assign epic name to a sub-task deceives the object of smart planning. Currently our subtasks are visible in different swimlines than the parent one because we are unable to link them to its epic link.
Please add this feature as soon as possible to easy our planning. As suggested by your support team, I'm voting on this issue and leaving you a comment to hopefully help prioritize this development. This feature is long overdue and there's no reason why you shouldn't give project managers the option of working either way even if your team doesn't believe is the ideal.
I'll look forward to the update.
Dear Customers,
After comparing this bug request against the known report JSWCLOUD-8181 we realized that both are addressing the same scenario. Since we consider JSWCLOUD-8181 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes in the original request so we can measure the impact and interest more accurately.
Cheers,
Belto
ATLASSIAN | Cloud Support Engineer | Amsterdam