nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Associating Issue type Scheme for an already existing project

Ivan Velarde

Hello, I recently encountered a problem when using the JIRA software. I created a new Issue-type scheme and I want to associate those issue types with an existing project that already has an issue type scheme. When I want transfer the old issue types to the new issue type (Issue Type Migration) I get an error message. Referer URL: http://p1141596:8080/secure/admin/MigrateIssueTypes!start.jspa com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=10005] I noticed that in the LexoRank Management and have the same field ID that needs to be rebalanced. Is that the issue or it is something else causing the problem. Thank You

Accepted answers

All comments

Moses Thomas_08kyb0

@Ivan VelardeI think Data in "AO_60DB71_LEXORANK" table is corrupted and needs to be fixed see how to solve problem here

Cannot reindex jira due to Expected exactly 2 rows the maximum marker row and the lowest ranked row for rank field

Best!

Ivan Velarde

@Moses Thomas should I rebalance the field ID?

Danyal Iqbal

Yes and please take a backup before you start

Danyal Iqbal

If this is a virtual machine, I would create a snapshot of the whole machine as a backup and restore it latere if anything goes sideways. If it is not a VM, you can create a backup of the database according to the documentation of your individual DB.