-
Suggestion
-
Resolution: Duplicate
-
2
-
When sub-task is created, it doesn't inherit the Epic link from the parent. This creates some issues, like:
- If a board is configured to use Epics swimlanes and you have visible on this board an Epic, and under this Epic a story and a sub-task under this story, if by some reason the story is not visible on the board (due to filter conditions or status mapping configuration), the sub-task is displayed under the "Issues without Epics" instead of being displayed under the Epic linked to its parent
- This also causes time reporting to create orphaned hours for sub-tasks which have no epic.
Defining sub-tasks to inherit their parents' Epic link would resolve both problems
- duplicates
-
JSWCLOUD-8181 Sub-tasks should inherit the Epic Link of their parent
- Gathering Interest
- is related to
-
JRACLOUD-86257 Sub-tasks created inside a custom standard issue type appear as 'issues without epic' when using swimlanes based on epics on a board
-
- Closed
-
-
JSWCLOUD-8181 Sub-tasks should inherit the Epic Link of their parent
- Gathering Interest
-
JSWCLOUD-11823 Filtered Sub-tasks should not appear in "Issues without Epics" in Agile Board Work View
- Gathering Interest
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