...
To achieve this in Jira, teams use Issue Link “is parent of” or “is child of” between Issues, instead of Epic Links. Because Epic Links can’t be chained between many levels. Issue Links doesn’t have any restrictions on chaining/levels. There may also be Issue Links for Dependencies or Blocking or Related.
Some teams also use Advanced roadmaps which allow to create levels above Epics.
And then to have more control on your project timelines, there is a need to strengthen your processes, to track your bottleneck issues. You need to see which issue has spent most time in which status or with which assignee, and take appropriate actions. Also you need to see where your resources are spending their time.
...
Get an aggregate view of a project Epics in a nested tree. Sum up your Epic’s Time Spent, Original Estimate, Time Remaining, and %age Complete. Edit all key Jira fields on the hierarchy screen.
Links Hierarchy
View up to 10 level of hierarchy based on your Issue Links. Sum up for Time Spent, Original Estimate, Time Remaining, and %age Complete. Edit all key Jira fields on the hierarchy screen.
...
The Portfolio/Advanced Roadmaps Hierarchy too can be visualized and tracked on this screen. For that you need to select your top level issue type, eg Initiative, from the “Issue Type” filter and select “Include Jira Hierarchy” from the additional search box.
...
Time in Status
Track your bottleneck Issues. Identify the issues which are taking more time by tracking their time spent in each status and time spent with each assignee, and take appropriate actions, with more than 7 types of reports.
Worklogs Report
...