Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-8181

Sub-tasks should inherit the Epic Link of their parent



    • 1
    • 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.


      We do internally developed software capitalization, and our time tracking must align to the epics teams are working on (in our world, epic=project). Because of this, we require all issues to be tagged to an epic. Sub-tasks cannot be viewed in the Plan mode, and therefore cannot be tagged to the epic. In addition, when I create a sub-task, it is not inheriting the Epic link from the parent.

      This causes our time reporting to create orphaned hours for sub-tasks which have no epic.

      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

      Please expose the sub-tasks in plan (or make it configurable), or ensure the epic link field inherits the epic attributes of it's parent!


        Issue Links



              Unassigned Unassigned
              jean.resener Jean Resener
              62 Vote for this issue
              45 Start watching this issue