Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Hi, Sprint Report shows issues as "as added" after i start the new sprint

Arun, Akila July 24, 2024

 

I closed the sprint today morning at 8.11am and opened the new one in few minutes around 8.15am. This is the first time I am closing and starting on the same day, few minutes apart. Whatever stories that got moved from the last sprint to the current sprint is reported as added issues to the sprint which is incorrect. Wondering if this is because of closing and starting the sprint immediately?

2 answers

0 votes
Arun, Akila July 25, 2024

When I closed the previous sprint, the pop up usually comes saying these are the 'unfinished' ones that will go under the next following sprint, and I hit OK to proceed. JIRA automatically pushed the 'unfinished stories (not done)' to the sprint following then I started that new sprint. This is how I usually did in the past with no issues but causing problems just this time.

Are you saying that you push the 'unfinished' stories manually to the future sprint before I close out the sprint? 

I think Jira wasn't caught up with the updating to the new sprint on those stories.  Or Jira had a glitch and that's why its showing that you completed one sprint & started the next one within few minutes. is that a possibility?

Lucas Lombardo
Contributor
July 26, 2024

"When I closed the previous sprint, the pop up usually comes saying these are the 'unfinished' ones that will go under the next following sprint, and I hit OK to proceed. JIRA automatically pushed the 'unfinished stories (not done)' to the sprint following then I started that new sprint." --> I confirm that I do the same on my side and it works properly. So yes maybe a glitch on your side...I hope it doesn't happen again!

0 votes
Lucas Lombardo
Contributor
July 25, 2024

Hello,

When you closed the previous sprint, where did you pushed the stories not done (backlog, future sprint waiting to start) ?

On my side I always close the sprint N-1, send the not done issue in the future sprint, and open the sprint N directly after and I do not have this issue, so it is not coming from the time between those actions.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events