Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Track sub-task progress

I am assigned a task that spans many sprints. Sub-tasks are created to manage progress within each sprint.

Is the parent sprint constrained to be in a sprint while any of its sub-tasks are in a sprint?

If yes, is it possible to leave some of the parent's sub-tasks in the backlog while other sub-tasks are in a sprint?

1 answer

1 accepted

1 vote
Answer accepted

When using Scrum and Sprints you do not assign sub-tasks to a sprint. You may work on the sub-task during a sprint, but it is the Story that is assigned to the sprint. As long as the Story has incomplete sub-tasks, it will not be considered done in any of the sprints. And you don't get partial credit for the story by completing sub-tasks.

You can have sub-tasks in the backlog while other sub-tasks are being worked on or completed in other sprints. But, again, you don't get story point/velocity/burn-down credit for those sub-tasks being completed.

The idea behind scrum, sprints, and stories, is that during Sprint Planning you are breaking down the work into Stories that are sized and scoped such that they can be completed during a sprint. It is the completion of Stories during a sprint that enable you to ascertain a team's velocity so that you know how much work (story points) can be completed by the team in a sprint. You use that information to plan future sprints so that your team commits to only as much work as you can actually get done.

You should not intentionally be scoping/sizing stories to span multiple sprints. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

399 views 19 23
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you