-
Suggestion
-
Resolution: Low Engagement
-
None
-
10
-
We only add estimates to subtasks, and not to both subtasks and parent tasks (stories.) This helps us avoid double counting of issue totals on Jira reports and pages. Unfortunately, there isn't a good way to group changes outside of an issue type such as epics or subtasks.
The Jira issue page has an option to include subtasks when seeing the original estimate. This would be helpful on the Details View while using the Agile boards. My stories with subtask estimates are showing 0 under the Estimate field; however, they are showing xx hours under the Remaining field. So, it's misleading that the "Estimate" field only shows the estimate for the main task or story; however, the "Remaining" shows the total remaining for subtasks as well.
- duplicates
-
- Gathering Interest
- is related to
-
- Closed
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[JSWCLOUD-9775] Jira Agile should show the subtask total with the Estimate field in the Details View
@Lynn_jira - given how Atlassian manages their product - I'd assume that this will never be fixed.
l
added a comment - Any timeline when we can expect this feature to be available in Agile board. ? We would like to have the estimate values from subtasks to be available in Agile board for main tasks.
l
added a comment - Any timeline when we can expect this feature to be available in Agile board. ? We would like to have the estimate values from subtasks to be available in Agile board for main tasks. l
added a comment - Any timeline when we can expect this feature to be available in Agile board. ? We would like to have the estimate values from subtasks to be available in Agile board for main tasks.
l
added a comment - Any timeline when we can expect this feature to be available in Agile board. ? We would like to have the estimate values from subtasks to be available in Agile board for main tasks. Not sure if it helps you guys, but we've just released the first version of our hierarchical view/editor (Epics/Stories/Sub-tasks) plugin for JIRA Agile, and it can make your Story estimations equal to the sum of sub-task estimations automatically.
You can try it here http://demo.plangle.io (just select a board and click on the "Plangle" button next to the Plan/Work/Report trio).
And of course you can download it from the Marketplace https://marketplace.atlassian.com/plugins/com.moresimp.plangle as well.
We are in the early stages of the development with a bunch of features in the queue and we are open to any suggestions, just let us know how we can help your processes and we'll include it in the upcoming releases.
+1 I'm having the same issues as described in the comments above. I want to use Remaining Time, but like this it's horrible.
Sean Smith
added a comment - Yeah, but does that one have a fancy screen shot? lol. I guess I shouldn't get too optimistic since the original issue is number 5471 and this one is 9775. It's been a long time and not been addressed. We have ended up creating Stories with original estimates and no remaining time. Then, subtasks with no original estimate, but with remaining time. This appears to have everything roll up as needed on the agile boards and within the issue summary (non-agile) pages.
Needless to say, gaming the system doesn't make me feel good about the product. It's very inconsistent and the reporting is miserable. We have had to write an entire web app to pull data using the API and present it in a readable format for clients.
Sean Smith
added a comment - Yeah, but does that one have a fancy screen shot? lol. I guess I shouldn't get too optimistic since the original issue is number 5471 and this one is 9775. It's been a long time and not been addressed. We have ended up creating Stories with original estimates and no remaining time. Then, subtasks with no original estimate, but with remaining time. This appears to have everything roll up as needed on the agile boards and within the issue summary (non-agile) pages.
Needless to say, gaming the system doesn't make me feel good about the product. It's very inconsistent and the reporting is miserable. We have had to write an entire web app to pull data using the API and present it in a readable format for clients. +1 for this request. It is definitely a problem in that there is inconsistency in the reporting of the time when using agile with time tracking. This is very troublesome and will prevent us from being able to use JIRA Agile as it will never correctly represent the correct original estimate unless this is resolved.
Please resolve this asap so that we can begin to use the Agile product. Thanks.
Many thanks for reporting this issue. We see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.
Regards,
JIRA Agile Team
Hi everyone,
Thank you for bringing this Suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap.
In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management