Agreed. It makes no sense that subtasks don't automatically inherit the Epic of their parent Issue. It's fine if you don't want to allow users to change the Epic of a subtask, but they should automatically inherit the Epic of their parent Story or Task. It causes problems that subtasks don't have epics. For example, when viewing a board separated into Epics, the subtasks are all just floating in an "issues without epics" section, which is ridiculous.

We need this for capitalization time tracking %'s as well 

Hi there,

With the latest version of Exocet, you can copy the links of the parent issue when you create a sub-task.
You just have to configure an operation like this:

and all the sub task that you'll create with this operation will be linked to the parent issue epic!

Of course, you can add condition to have this operation available only where you want it.  

We've just added the ability to do this with Automation for JIRA! It is simple to add a rule that listens for sub-task creation and then sets the Epic Link from the parent.

The rule would look something like:

This was done as part of work to make related issues easier to work with. For more details see https://blog.codebarrel.io/synchronize-parent-and-sub-task-issues-with-automation-for-jira-bdcca6c9d453

This should be done. Its would be a great bonus for all using Jira. This improvement will allow the overall status to be checked on instead of only seeing the parent issues. Right now we have no clue as to what is happening to the subtasks unless we go into each parent to check.

Come on Atlassian you can do better than this

Much needed improvement to sort issues in queries in a way that can be logically read by a human

This is a great idea. If implemented please implement in Kanban as well as Scrum.

Thanks!

Laurence - we are using Tempo combined with the new epic support. With this configuration, you can pull worklog reports that provide the epic link for each issue time was logged towards. With sub-tasks, you get the parent issue id, so you have do an extra step of looking up the epic link for the parent and adding it to the file. Then you can get a roll-up of all hours. Hope this helps.

+1.
in the meantime, how does anybody manage to get any stats for total number of hours per epic?

I would also like to see sub tasks inherit the epic from their parent.

We use projects to separate out key distinct systems, so we're looking to use Epics as significant projects, broken down into many Stories, and the Stories are broken down into sub tasks.

As a manager, I'd like to be able to see statistics for completed/remaining tasks in an Epic, rather than just direct descendants of an Epic. Additionally, I'd like the issue search to be able to filter by Epic to return everything associated with that Epic, both children and grand-children.

Finally, it would be good when viewing an Epic, to be able to hide closed tasks or at least sort by issue status.

I think most of these things would be relatively trivial once the sub-tasks inherit their parent's Epic.