Cost Tracker has the feature to automatically group Issues by their parent Epic, however this only works for Tasks/Stories and other top-level Issue Types. It does not group Sub-Tasks within that Epic.
When you work primarily on the Sub-Task level, this makes "Group by Epic" effectively useless. See attached example where I have logged cost against a Sub-Task but it does not group up against the Epic.
JIRA has the parentEpic JQL query which could be used to group Sub-Tasks into their respective Epics.
David Bruce
| Tempo Products | Cost Tracker for Tempo Timesheets, Tempo Reports |
| Tempo Platform | Cloud |
Attachments Open full size
I actually consider this a bug report, not a feature suggestion.
Now that Jira has streamlined the Story–Epic and Subtask–Story relationships, it makes sense to simply use that parent-relationship, even if levels above Epics have been introduced.
Porting the considerably more flexible Generators from Structure to Tempo would be even more awesome. One could then group the Cost Tracker entries by linked issues by a specific relation, for instance.
Attachments Open full size
It should be implemented as "parentEpic" via JQL imho
Attachments Open full size
Would reeeeeeally appreciate this feature. It would save me a lot of time.
Attachments Open full size
Agreed, this is must have for accurate reporting. JQL has the issuekey in portfolioChildIssuesOf(key) option which might allow the developers to make this happen?
Attachments Open full size
Would really like this too... our epic report is kind of useless without it.
Attachments Open full size
how frustrating that this isnt available - please do ti
Attachments Open full size
Added a vote for this. It's a non-starter for us using this tool because manually setting up groupings is double effort if it's already categorized in an epic. If the grouping is by epic and sub-tasks don't role up, then what's the point of the epic grouping.
Attachments Open full size