Page Comparison

Step-by-step guide

...

1. it's necessary to configure Parent Issue Link: Epic Link in Add-on Configuration. 

   Info
   Add-on configuration is accessible from the report by Administrators only. See Configure link in header part of the report page.

   

2. Then, with Sum Sub-Tasks gadget report option enabled, it will aggregate hours for Epics.

   Info
   Note, behaviour is quite the same as it used to be in Timesheet Reports and Gadgets add for Jira Server using Group by: Epic Link. But in Jira Cloud, either Group by Epic Name or Sum Sub Tasks options should be used to get correct results.

   However, if you'll want to Sum Sub-Tasks not to Epic, but to parent issue only, you will need to adjust add-on configuration each time. Grouping by: Parent in case of Parent Issue Field configured works quite the same, i.e. sums hours into issue via Epic Link too.

   Here is example of report grouped by Worked User, and all hours summed into epic:
   Image Modified

Please note, parent may be calculated up to 3 or even 4 levels, parent of a sub-task, Epic of a Story, if Parent Issue Field is configured in add-on configuration, Linked Issue, if Composition Issue LInk is configured in add-on configuration, and finally Jira Portfolio issue type, if Parent Issue Type configured in add-on configuration.

...

Note, it may be convenient to use use use Filter with JQL like "parentEpic in (issueKey,...)" in case you'd like to have report for certain epic(s).

...