Hello,
I'm getting the error
com.atlassian.greenhopper.service.rank.RankException: Multiple heads found in rank chain: issueIDs [[43872 r0 no prev n43873], [48411 r0 no prev n48420]] have no parent link. Please update the rank table and ensure that there is exactly one issue that has no child and exactly one that has no parent.
Searching the internet, this seems like a known issue but the resolution was never posted. Has anyone else fixed the issue and has the query?
Thank You.
Hi Ricardo,
I resolved the issue by truncating the table. Jira rebuilt it and now the agile boards are working again.
Thank you for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can run this query at your db:
select * from "AO_60DB71_ISSUERANKING" where "NEXT_ID" not in (select "ISSUE_ID" from "AO_60DB71_ISSUERANKING");
That way you will be able to identify the issue id, if there is an issue causing this problem. After that we recommend that you open a new ticket in SAC, once you will probably have to send them your backup to run some scripts. Please attach the results of the query.
I believe your issue is related to this kb: https://confluence.atlassian.com/display/GHKB/The+tail+end+of+the+GreenHopper+Global+Rank+is+missing.
Cheers,
Ricardo Carracedo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ricardo,
I ran your query and it returned 0 results. It looks like the problem is that there are two issues in the table that have no siblings. Esentially they are orphaned. I'm afraid if they are removed, they will just cause the same problem for the issues that they are siblings of.
Any other ideas?
Thanks again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Amichaels
In that case, it is probably related to this article: https://confluence.atlassian.com/display/GHKB/Multiple+heads+found+in+rank+chain
And you will have to open a ticket in SAC, once they will need to restore a backup of your instance, identify the custom field of your rank chain and run some queries to identify where it is broken.
Cheers,
Ricardo Carracedo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.