How to display estimate time or time spent on feature/epic

Question

Hello everyone,

I am using primarily features for "higher" items and then i create stories/spikes that i put as "realated to" or "realizes" feature, so these items are linked to the feature. I am looking for a way how to see combined time ESTIMATED and SPENT for these items that are grouped under a feature (ideally no matter whether it is realized by or related to).

Also, stories / spikes that are related to particular feature might have another items related to them (sub-related?) and therefore the whole hierarchy grows e.g.

feature -> story/spikes -> bug/spike/story

and my aim is to display combined time estimates and time spent for everything that is being linked to each other in any way...thank you in advance.

Hannes Obweger - JXL for Jira · Answer

Just to expand on the last point, this is how this could look in the app that my team and I are working on, JXL for Jira; all issues relate to their nested issues via issue links of a particular issue link type:

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for configurable issue hierarchies (based on Jira's built-in parent/child relationships, and/or based on issue links), issue grouping by any issue field(s), sum-ups, or conditional formatting. With these, you can build a view like the one above in just a couple of clicks.

Any questions just let me know!

Hannes Obweger - JXL for Jira · Answer

Hi @Michal Macko

while it isn't available out of the box in Jira, I can think of two ways forward:

* One option would be to sum up the values using Jira Automation and write the result into a custom field on your higher-level items. I always find this article a good starting point - https://community.atlassian.com/t5/Jira-Software-articles/Calculate-the-sum-of-original-estimates-of-all-issue-types-to-an/ba-p/1660572 - however you'll likely need to make some modifications due to your specific requirements, especially the "nested" nature of your dependencies.
* Alternatively, if you're open to options from the Atlassian Marketplace, you should be able to find more specialised solutions there. I myself happen to work on an app in which your use case should be relatively easy to solve; I'll provide more information below.