My team have recently started using Story Points. We are currently entering items in Jira where we enter the requirement from the Business as a User Story and are then detailing the Technical Tasks as sub-tasks to complete it. At the sub-task level we assign the story points. These however, don't seem to sum up into the Story. Which then aren't reflected in the reports (e.g. burndown charts) and also aren't detailed in the Summary of assigned work. So in theory I could manually go in and sum up these myself and put them at the Story level so that the reports work right? To make things more confusing though if I go into Portfolio and find my sub-task story points are summed up to the story. I can then 'overwite' the story points in there, but they are then displayed as double (story points on the story + story points on the sub task). When I then commit my changes the stories in my projects are updated from portfolio with my manual value - the auto summed up values. Why aren't Story points firstly auto-summed up in issues from sub-tasks (e.g. like time estimation is) and if it is possible how can I achieve this? If this is not, why does Atlassian have two different approaches?
Try our Great Gadgets plugin. It offers a suite of gadgets like sprint burndown, release burndown and velocity that have an option to include sub-tasks in the calculation.
The plugin is available for both Jira Server (https://marketplace.atlassian.com/apps/1218777/great-gadgets-for-jira-server?hosting=server&tab=overview) & Jira Cloud (https://marketplace.atlassian.com/apps/1216564/great-gadgets-for-jira-cloud?hosting=cloud&tab=overview).
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.