You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a project wherein the stories are Developed and Tested within the sprint but are deployed on Prod at least a week or two after due to PO Approval UAT Testing and Production deployment process, etc. Sometimes Prod deployment happens with features developed in 2-3 sprints ( as part of a single Release)
We have another Kanban board where we track the statuses after QA.
So it goes like this:
Board 1: To Do --> In Progress --> QA --> Ready for PM Acceptance
Board 2: Ready for PM Acceptance - UAT - Prod - Done
As for our team, we have completed the work picked up in the sprint so it is 'Done' for the Sprint. However, when we close the Sprint after testing, the stories/issues are not considered as completed by the Sprint Reports. Jira still considers them as Spill overs and it impacts the velocity.
How do we handle such scenarios? Any suggestions / advice is truly appreciated. Thanks in advance!
As my understanding you need to set the sprint goal and the start and end date then it will show like this.i Hope this will help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.