Yep, it's a quirk of the lexorank system, which can happen when an issue and the issues around it have been repeatedly re-ranked in a similar area. It's a bit more complex than this but you could say "it's run out of gaps to move things into". It can also happen if the database or index get damaged by something (frankly, it's almost always the index)
Try this sequence:
This usually fixes a broken ranking and will let you delete again.
You may find lexorank indexing errors in the logs in the first run, but it will complete. Don't worry about those errors, they should go away when you hit step 3.
(If you only run project re-indexing in step 1, then this may not work - if it does not fix it, then run step 1 again but with a full re-index)
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
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