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

Your Points Tracker
  • 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
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?
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

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?



Log in or Sign up to comment

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