Need help on user stories

Rahul_gb31nc

My scenario is i have a user story which has 3 subtasks. Each subtask is having one story point each. I have wrote a automation like auto-sumup subtasks story points to user story. So now the parent story point of this 3 subtasks have 3 story point. 

For suppose when I close 2 subtasks at the end of the sprint and one subtasks is still in progress. So here team have achieved 2 story points but in the report it shows team achieved 0 story points on this user story as user story still in inprogress as one substak in not closed yet.

When I move this user story to next sprint, the user story should be moved with only pending subtask and not with closed subtasks and the story point of the user story should be only 1 as only one subtask is pending

 

 

 

 

Walter Buggenhout

Hi @Rahul,

Jira does not work that way and there is some best practice behind that to keep in mind.

A story - by definition - is a feature (a piece of working software) that you deliver as a whole to your users. In order to develop that piece of software, you may need work from different areas of expertise (like e.g. backend stuff, frontend coding and UX), but it can only be released as a whole. For your users, you have not delivered anything as long as you have not shipped every single part of it.

Jira configuration is built on top of that principle. And so, essentially, you should add an estimate of 3 story points on the story (not on the sub-tasks) and be aware that - indeed - as long as not all sub-tasks are complete, nothing is considered to be delivered. The completed sub-tasks move along to the next sprint as they provide context to the rest of the story and insight into where your story development progress.

If it appears that your sub-tasks are stuff that can be delivered separately and as value to your users (and can be shipped separately), that may indicate that you should consider defining them as standalone stories inside an Epic, rather than as subtasks to a story.

Hope this helps!