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,459,752
Community Members
 
Community Events
176
Community Groups

How to Handle Jiras Where Testing May Not be Completed Immediately

Sometimes we'll have development efforts that may take a full sprint and testing may not occur until a subsequent sprint. I currently have two goals that I want to meet, but seem mutually exclusive.

I want to be able to know that in, say, Sprint 10, that we did the 30 story points of development. However, if I close out Sprint 10, and I haven't closed out the Jira because testing isn't complete, then Sprint 10 loses all record of those story points being completed.

If I close out the Jira before closing out the sprint, then it falls off of the testing radar.

 

Any advice on how to handle situations like this?

0 comments

Comment

Log in or Sign up to comment