Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
I have issue closed in previous sprint and it appear in active sprint.
During planning the sprint issue are not visible in plan mode. After click 'Start sprint' issue are visible on board.
Do you have any ideas/hints why is it happening?
The behavior I am noting with this issue, that I would like resolved, is stories and bugs from the backlog that were closed but not associated with a particular sprint are added to the next sprint we start. This is particularly frustrating to the team as it clutters the sprint with items that have already been closed and often marked as Duplicates oir Won't Fix. The workaround I have found to resolve this is to reopen all these items, move them to another sprint, reclose them (with the same status), and then end the second sprint I created. This disrupts our velocity reports but cleans up the current sprint.
In our case problem was that we had 'Sprint' field not empty.
When we planed sprint, sometimes we decied close some issues. When we close issues but not clear Sprint field it appear in sprint which was set in Sprint field. If we cleared this field before close issue everything was ok.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs