Forums

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

Stories did not roll over when active sprint was completed

Juan Martinez
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 10, 2020

Hi All, 

Today i completed my active sprint in JIRA and noticed that not all stories rolled over into the next sprint (Even though i did selected them to roll into the next sprint and i did want all stories in the project in the active sprint to roll). I had to go back and find the missing stories and bulk move them into the new sprint. One thing i did notice when i found the stories was that they still contained a reference to the now closed sprint even though the stories that did roll over had something like "Sprint : Sprint 1, Sprint 2". That proved to me that those stories did in fact not roll over. I've been thinking about what could have caused this and my only conclusion/lead was the below:

I have 1 main project that has all the stories. Within this project i have created/configured multiple boards that contain their own saved filters but that run off the same sprints. I "completed" my active sprint today from the board with a more detailed filter (i.e board 1). 

 

ex:  

Board 1 = Filter is (Project in (ABC) AND ("Custom field" in (agileteam1) OR assignee is EMPTY)  and issuetype in standardIssueTypes() ORDER BY Rank ASC )

 - This returns 10 stories

 

Board 2 = Filter is (Project in (ABC) ORDER BY Rank ASC)

 - This returns 30 stories

 

Should i have completed the sprint from board #2? 

 

 

1 answer

0 votes
Hernan Halabi - Elite IT Consulting Group
Community Champion
March 10, 2020

Hello @Juan Martinez welcome to the community. It would be better to start and close sprints from the second board since that one contains all stories. 

Personally I prefer to have only one scrum board per project so I'm certain that I don't mess up with the Sprint. All the other boards can be kanban and I could filter for active Sprint as well to see a little part of what was scheduled for the Sprint.

If you need multiple scrum boards I would suggest not to show the same issues on them to avoid scenarios like this one.

Suggest an answer

Log in or Sign up to answer