The users loaded up their sprints with stories on the Friday before the upgrade. The sprint is set to start on Monday.
Checked after the upgrade and all the stories are missing from the sprint . They are in backlog though.
Any Ideas on why the stories moved out of the planned sprint after the upgrade?
Other than asking everyone to move their stories back into the sprint what else can I do?
Hi @Chris Szorc
Are you sure that nobody by mistake removed the stories? Could you check the history of couple of tickets? Maybe there could be some information?
Overall from which version you upgraded? Are you a System Admin? Did you do the upgrade or someone else?
@Mirek - The Sprint names are intact in the "Sprint" field of the Stories. However, the stories aren't showing up in the actual "Active Sprints".
P.S: I work with @Chris Szorc in the same organization where we are facing the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to understand... @Chris Szorc mentioned that the tickets after upgrade are showing on Backlog, you mention that the stories do not show on "Active Sprints".. So did the sprint actually start? Tickets are showing in Active Sprints only when there is a active sprint.
Could you check the filter that is used on the specific Board? This filter should show all the tickets that you want to view. You should check it always separately by using Issue Navigator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mirek - Issue is with both Active and future sprints. Though issues are tagged to sprints they are not showing up in the respective sprints, instead all of them are listed in backlog.
If the sprint names are re-entered in each issue manually (the same value) it works. But we need a systematic way of getting this update done for all issues.
Suspect something to do with the refresh issue after the upgrade.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Chris Szorc and @Saravana
Please check if you are not hitting this problem (related to swimlanes and Epics)
https://jira.atlassian.com/browse/JSWSERVER-11318
If so then check this KB for resolution
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The issue was resolved by doing an index on the project that was having the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.