You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.