Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot delete a JIRA 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 fieldFAILEDChecks 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 checkFAILEDChecks whether the marker rows for a rank field have the expected rank value.
Marker rows in valid bucket check.FAILEDChecks 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

 

1 answer

0 votes
Mirek
Community Champion
March 12, 2018

Oh.. You might be facing this - https://confluence.atlassian.com/jirakb/cannot-reindex-jira-due-to-expected-exactly-2-rows-the-maximum-marker-row-and-the-lowest-ranked-row-for-rank-field-779158916.html which requires more investigation. If the normal reindex is failing and you tried many times the best option is to read above KB and later contact support if you are not sure what might be the root cause affecting your instance.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events