Error 500 when bulk changing issues


During the Bulk Change operation inside a project we receive an error... to reproduce it we have to tick several non-epic objects, select "Move Issues" and then move for examples Bugs to Issues etc, once you click on it Error 500 with the following message appears

"com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=10005]"

We tried following this guide as it seems to be the very same issue we have

The guide worked fine until after the Diagnosis, naturally we didn't find any endmarkers for the rank ID 10005 (or any line at all for this ID actually) so we tried to execute the mentioned resolution

mysql> insert into AO_60DB71_LEXORANK values (DEFAULT,10005,7,-9223372036854775808,NULL,NULL,'0|000000:',0);
ERROR 1062 (23000): Duplicate entry '7' for key 'PRIMARY'

As you see we receive a duplicate error for this line, unfortunately the knowledgebase article doesn't offer a solution for this as nowhere is the required information which ID one should try instead

Thanks in Advance


2 answers

1 accepted

0 votes
Answer accepted

Alright, Branden McElveen's suggestion didn't provide a solution for me, but it led me on the right track... as it turns out it seems like the LeoxRank system has failed to properly initialize and thus pretty much all the initial markers were missing, the workaround suggested in the following bug report helped and now everything works just fine:

Thanks for circling back and letting us know what the resolution was.  I'm happy to hear all is well!



Hi Nikolai,

At that point you can skip it and go to the next query.  If you still get those errors:

  1. delete from AO_60DB71_LEXORANK
  2. Go back through Several actions such as issue ranking, move, export are failing
  3. Re-balance JIRA under System Administration > System > Advanced > LexoRank Management



Sadly none of the adviced solutions worked, by the way running the integritiy check on the LexoRank management seems to return failures on all field ID's except 11300


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

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...

600 views 0 7
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you