Why 'Commitment' story points change when US is moved out of sprint?

[Abhishek Chaudhary]

So I had started the sprint with 22 SP, then after 3-4 days, I moved 1 US worth 1 SP to backlog & added a new US worth 3 SP. 

With the above changes, I hoped that after sprint is completed, the 'Commitment SP' would be 22 & 'Completed SP' would be 24. 

However, it's showing 'Commitment SP' as 21 & 'Completed SP' as 24.

Can anyone help as to what happened there with the 'Commitment SP'? Why its showing incorrect? Thanks!

[Colin Goudie · Accepted solution]

The closest you probably will get to at the moment is using linked issues. If you are using greenhopper it can aggregate multiple linked issues and their subtasks up. (I.e. And epic) however, that is still only by oe project. On the near horizon though is rapid boards in greenhopper. This will be able to let you manage issues spanning projects, but I would imagine it still may feel lacking to you since the rest of JIRA doesn't.

[Colin Goudie]

The Rapid board looks awesome, once it's released, I would imagine 90% of your use in JIRA will be via that anyway :)

[Taber Loveless]

Good to know... I thought about trying out Rapid anyway. As for not working throughout Jira thats ok as long as there is one place to see everything aggregated for a high-level view.

[Igor Sereda [ALM Works]]

If you need time aggregated, then the links won't work - unless you have time aggregation based on links (probably that's what Links Hierarchy Report plugin does - have to check).

I was also asking out of curiosity if we can make our Structure plugin help in such case. With Structure you can organize issues from multiple projects in a hierarchy, and have time aggregated upwards. But our plugin is commercial and the integration with GreenHopper is limited so far -- so I'd suggest trying Rapid boards first and seeing what that feature could evolve into in the nearest future.

[Taber Loveless]

Are 'linked issues' the best practice for this in Jira?

I tested this by adding "Feature X" to 1 project then all other tasks as 'issues' in the appropriate project.
The issue I see with this approach is that the Agile Planning screens do not show/include any linked issues from other projects or thier time estimates.

Subtasks would be nice as it would be easier for planning/review but I dont see how Jira can support this without the ability for 'versioned components'.

Thoughts? Suggestions?

[Igor Sereda [ALM Works]]

Do you need A B C D to be sub-tasks? What for? Can they be just separate issues linked to the Feature X?