Loading...

XML

Word

Printable

UIS:
2
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

is related to

JSWCLOUD-16752 Sub-tasks created inside a custom standard issue type appear as 'issues without epic' when using swimlanes based on epics on a board

JSWCLOUD-8181 Sub-tasks should inherit the Epic Link of their parent

JSWCLOUD-11823 Filtered Sub-tasks should not appear in "Issues without Epics" in Agile Board Work View