LexoRank Exception, cannot delete an issue

ETiC
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 12, 2018

We cannot delete an issue from a JIRA project. We got an exceptin pop up. The call stack looks like the following (see below). In addition LexoRank integrity checker is reporting some errors:

 

Report for rank field Rank, FieldId=10005 at Mon Mar 12 2018 14:00:07 GMT+0400 (Arabian Standard Time)Run

Marker rows present in table for rank field FAILED Checks if the rank table has been properly initialized for the rank field. A minimum and maximum marker row are expected to be present in the table for the rank field.
Marker rows correctness check FAILED Checks whether the marker rows for a rank field have the expected rank value.
Marker rows in valid bucket check. FAILED Checks if the marker rows of a rank field are in valid bucket(s).

Call Stack

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=10005]
at com.atlassian.greenhopper.manager.lexorank.LexoRankDaoImpl.getMaximumMarkerRowAndPreviousRow(LexoRankDaoImpl.java:399)
at com.atlassian.greenhopper.service.lexorank.LexoRankOperation.rankInitially(LexoRankOperation.java:181)
at com.atlassian.greenhopper.service.lexorank.LexoRankOperation.execute(LexoRankOperation.java:120)
at com.atlassian.greenhopper.manager.lexorank.LexoRankManagerImpl.performRankOperation(LexoRankManagerImpl.java:300)
at com.atlassian.greenhopper.manager.lexorank.LexoRankManagerImpl.getRankOrRankInitially(LexoRankManagerImpl.java:86)
at com.atlassian.greenhopper.customfield.lexorank.LexoRankCFType.getValueFromIssue(LexoRankCFType.java:121)
at com.atlassian.greenhopper.customfield.lexorank.LexoRankCFType.getValueFromIssue(LexoRankCFType.java:29)
at com.atlassian.jira.issue.fields.ImmutableCustomField.getValue(ImmutableCustomField.java:350)
at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper$DeletedIssueEventData.collectCustomFieldValues(DefaultIssueDeleteHelper.java:288)
at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper$DeletedIssueEventData.<init>(DefaultIssueDeleteHelper.java:275)
at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper.deleteIssue(DefaultIssueDeleteHelper.java:120)
at com.atlassian.jira.issue.managers.DefaultIssueManager.deleteIssue(DefaultIssueManager.java:719)
at com.atlassian.jira.issue.managers.RequestCachingIssueManager.deleteIssue(RequestCachingIssueManager.java:232)
at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:402)
at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:378)
at com.atlassian.jira.web.action.issue.DeleteIssue.doExecute(DeleteIssue.java:23)
... 1 filtered
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63)
... 7 filtered
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
... 52 filtered

4 answers

0 votes
earnestware April 13, 2019

have the same problem, any ideas?

0 votes
pmayor September 14, 2018

Anyone has fix it?

0 votes
Victor Goldaracena
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 8, 2018

Did you manage to fix it? i been working on this, but i cant find anything about it.

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 12, 2018

Hello,

Please have a look at this article and its resolutions and see if it helps resolve your issue.

Regards,

Shannon

Suggest an answer

Log in or Sign up to answer