We just spent ages prioritising our backlog and moving everything to the correct place by Rank, then we moved some tasks into Sprint 3 to check the total estimate counter (we are currently on Sprint 1).
As soon as move around 10+ tasks into that sprint, it reversed the Rank order when they were in that sprint. When we moved it back into the backlog the order stayed reversed.
What's worse, is we thought that perhaps hitting refresh will get them back to the order they were supposed to be originally.
However, this actually caused the order of the ENTIRE backlog to mess up, with different stories jumping to completely random locations, some staying where they were etc.
So obviously all of our work prioritising the backlog was lost, and we really need the solution asap, in order to unblock us to re-order the backlog safely again.
This just happened to us as well. We were in the middle of prioritizing our backlog. Stepped away for a little bit. When we went back to it, lots of issues landed in different spots. Definitely did not preserve a lot of ordering work we went through. It is definitely not a filtering effect. All of the issues currently have the same priority. I'm assuming the backlog would prioritize the actions of manual ordering but what just happened would suggest otherwise.
@Lynne Liu Any additional learnings or insights to share after posting this 6 weeks ago?
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events