-
Suggestion
-
Resolution: Answered
-
OnDemand
-
64
-
193
-
NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.
Hello all,
Thank you for watching, voting, and commenting on this issue. We understand this has been a long long long running request. We also understand this has caused a lot of frustration so I don't want to ignore that fact, but I do want to strike a chord of optimism with this update.
As John mentions in the comment below - the automation team have been busily building out an amazing library of automation rules which cover a massive range of use cases.
Summing estimates from subtasks to stories is one of these rules and here is the link to how to create this rule...
https://www.atlassian.com/software/jira/automation-template-library/sum-up-story-points
Please note there is no limit to the number of rules that you can execute within a single project.
We do have plans to bring more of these rules from the public library into the in-product automations library, but for now you must replicate the rules manually.
We're really interested to get your feedback on the success / gaps of this solution so please let us, as well as all other interested users, know here.
Thank you,
Eoin
Product Manager
Summary
As a Greenhopper Scrum product owner, I want story estimates to automatically total to the sum of the estimates for all sub-tasks IF and ONLY IF subtasks are entered (else I want story estimates to be manual entry) so that I can view on the scrum board the original estimate against the remaining time.
Definition of Done:
1) When no sub-tasks exist for a story, the estimate field for the story allows entry of a value manually
2) When one or more sub-tasks exist for a story, the estimate field for the story is calculated as the sum of the estimates for all sub-tasks for that story
Context:
I'm finding a feature in Greenhopper to NOT operate as I would have expected. The feature is in estimating where the estimation on the scrum board is configured for original time estimates. What I would like is:
1) when no sub-tasks are created for a story, the estimation and remaining fields are editable within the story
2) when sub-tasks have been created, the story estimate and remaining fields are calculated as the sum of the estimate and remaining fields for the sub-tasks
What's currently happening is that the story estimate field is not calculated from the sum of the sub-tasks but the story remaining field is. Worse, if you enter a value in the story estimate field when sub-tasks have been added and estimated, the value entered into the story estimate field is added to the story remaining field, which already has the sum of the sub-tasks. Thus, if, as a work around, you try to manually enter a story estimate that equals the sum of the sub-task estimates, the story remaining field value doubles. There's no work around for this. This feature seems poorly defined. I understand what the product team was trying to accomplish... the ability to estimate and view remaining values for stories that have no sub-tasks or prior to sub-tasks being added. What they missed is that the field could serve both functions - manual entry when no sub-tasks exist and calculated value when sub-tasks do exist. I strongly urge the product team to consider this feature at their earliest opportunity as the inability to see from the scrum board the original estimate against the remaining value in plan and work mode is a problem.
Steps to reproduce
- Configure Scrum board to use "Original Time Estimate" for Estimation Statistic
- Configure Scrum board to use "Remaining Estimate and Time Spent" for Time Tracking
- Create an issue with issue type Story, without specifying any Original Estimate and Remaining Estimate
- Create 2 sub-tasks for this issue.
- Sub-task 1 has Remaining Estimate of 4 hours
- Sub-task 2 has Remaining Estimate of 2 hours
- Checking parent of sub-tasks in Issue View, Original Estimate and Remaining Estimate is now shown as 6 hours
- Navigate back to Scrum board, open Issue Detail View, and Original Estimate for parent issue is Unestimated
- details
-
- Closed
- incorporates
-
JSWCLOUD-16199 There isn't consistency for the Original and Remaining Time estimate fields on Time Tracking gadget and the Board backlog
-
- Closed
-
-
- Gathering Interest
- is duplicated by
-
-
- Closed
-
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Future Consideration
-
- Not Being Considered
- relates to
-
- Closed
-
- Closed
-
- Gathering Interest
- was cloned as
-
- Closed
- derives
-
SW-5042 Loading...
- mentioned in
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-92573] Sum estimates from sub-tasks in user stories
@Eoin Unless Atlassian thinks that the customers are fools, you are not going to fool anyone with this automation solution that does not work well for most use cases. Why don't you agree that not giving the basic features is a way to make more money for Atlassian and that this unethical way is your business model itself - apart from forcing to buy the plugins for the whole Jira instance and not allowing it for a project or a set of users ?
Atlassian is infamous for its dirty business model. They intentionally leave out mandatory and basic (very very basic) features/functionality to get more money from 3rd party plugins which are also paid per user.
+1. The lack of this functionality is becoming a decision maker to move out of Jira in my company.
Hi Ahmet & everyone,
we were struggling with absence of this functionality & created 2 add-ons that enable such functionality
Sum it up - enables Sum up Story Points (or any value in general, including time-tracking) all the way from Sub-task to Epic - easy to configure ** **
https://marketplace.atlassian.com/apps/1219877/sum-it-up?tab=overview&hosting=cloud
OR
Advanced Analytics - sum up data & visualize in a table or different charts to easily understand your data in a meaningful way
https://marketplace.atlassian.com/apps/1226112/advanced-analytics?tab=overview&hosting=cloud
Hope this helps! If you have any questions, please let me know.
Thanks,
Richard
Faced the same challenge with viewing story points and estimates within Epics. We developed a plugin that might help. It shows total story points, time logged vs. estimated, and epic progress. We've found it super handy. If you're curious, you can check it out https://marketplace.atlassian.com/apps/1231982/epic-insights-issue-view-for-jira?tab=overview&hosting=cloud&utm_source=jira&utm_medium=backlog&utm_campaign=JSWCLOUD-9167
Cash grabbing st company. Basic features and serious bugs never fixed or implemented.
Such a ridiculous solution for a very common use-case. "Oh, we support sub-tasks but for estimations, you have to do it manually. So, we also end up updating the burndown manually. If you still insist, we give you a complex workaround and you end up spending more time yourself and we will not spend that time ourselves""
Great customer support and treating 1000s of users enterprise customers as cr ap. Good going Atlassian, as always. Half baked solutions and half baked reports.
Then we have to rely on third party extensions for which you will again ask to license for the whole Jira instance and not per project or for a limited number of users who will actually use the third party extension.
Thanks nkojuharov1091490796. Although the answer doesn't represent native support for this suggestion - automation is the best way to solve subtask story point roll-up and will be the only way to solve this for the foreseeable future. We are looking to make a shift in how we communicate back to you on suggestions (particularly long running suggestions) and we do't want to mislead people in believing some change might come where it is currently not the focus of our team. Out current focus is on improving performance and scale; and there is lots of exciting change coming in Team Managed Projects, Roadmaps (including Advanced Roadmaps), and Insights.
Thanks
Eoin
This is a major frustration on our part, and are actively looking for alternatives