This question is in reference to Atlassian Documentation: Creating and deleting work items
In Portfolio, why does Scope allow you to enter story points for sub-tasks (and sum them to the parent Story) but then issue a warning on commit about being unable to commit story points? Should we enter story points for sub-tasks?
Hi Roger, this really depends on your estimation process. Agile out of the box does suggest NOT to estimate story points on sub-task level, but keep them on the story level only. The views and reports on agile boards are currently optimized for that. However, we see some teams have a need to estimate more fine-grained nevertheless, thus this is a popular feature request for boards to support better sum-up of subtask story points.
As it is today: If you don't have an urgent need to estimate sub-tasks in points, I'd recommend not to do it. If you have a need, you can actually add the story point field to the sub-task issue type. In this case, the commit from Portfolio to JIRA will also succeed. The limitation however is that the agile board does not deal explicitly with the aggregation, so your velocity reports won't consider those story points from the subtasks.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs