Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,545
Community Members
 
Community Events
184
Community Groups

How to filter the DONE tasks and not carry over to next sprint even though the user story is INPROG?

I have a user story which is "In Progress" at the end of the sprint. Let's say I have created 50 Tasks/Subtasks in that user story & I completed 40 Tasks/Sub Tasks. 

When I go to the next sprint, I see all these 40 also carried forward along with the user story. How can I stop this & take only those 10 Tasks/Sub Tasks which are not done to next sprint. 

I should not be seeing all these 40 tasks in DONE column at the start of the sprint itself.

How can I achieve this ?

1 answer

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 03, 2023

Hi @Suganya ,

unfortunately, the way Jira scrum boards work is it to assess at the story or task level not the subtask level. So, unless all subtasks within the story are complete then they will all be moved back to the next sprint or backlog. One way to better manage this is to break your stories into smaller bits of work with fewer sub-tasks.

I completely agree with you, but on some cases, when it overspills we face this issue. 

Do we have any configuration to show only the user story & not completed tasks in the board & hide the completed ones which are in DONE state ?

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 03, 2023

You could creat a quick filter to hide completed subtasks, e.g. type = subtask and resolution is not empty. Of course this will hide newly completed subtasks in the current sprint. You could add a time component to help with that but it would need to change with each sprint.

sure, Thank you for the quick info. 

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 03, 2023

Another idea...

create an automation that triggers on a sprint completing. Add a label to any sub task that was completed. Then your quick filter could filter out anything with that label. 

That's great idea. I'll try this for such scenarios. Thank you so much. 

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 03, 2023

You are most welcome. If this does address your question, please consider accepting the answer.

Sure, Definitely. 

Suggest an answer

Log in or Sign up to answer