Moving an issue in JIRA between projects

Dear Community,

I ran into a problem to move an issue to a different project. It caused the problem with a MySQL permissions. Changed password to one without special characters. The problem with the DB seems have been solved but now I'm getting another exception:  


com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field


Reindexing doesn't help. Any ideas ? 


Best regards,


2 answers

Thanks a lot, Mikael.

Unfortunately the workaround didn't help. Every time when I add manually rows in AO_60DB71_LEXORANK for one rank id reported in the exception, then re-index JIRA, the next attempt to move the issue throws the same exception but with a new rank id. So I have to maually import once again the ranking rows for this id, etc.... 


More ideas? 

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

612 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