can't delete issues in jira

[Children Services IT]

I am not able delete any issues that I create. I am in as Admin or project admin.

Technical details

Log's referral number: 1dd770be-63aa-4d70-9f4c-d75746ad56d7
Cause

Referer URL: http://itdjira.csd.toronto.ca/secure/RapidBoard.jspa?rapidView=7&projectKey=TEST&view=detail&selectedIssue=TEST-1

[Scott Theus]

Bonita, your log file won't open, the page is not available. Can you describe the error or what is happening when you try to delete the issue?

-Scott

[Nabil]

Hey Bonita,

Can you see the project permission if you have the Delete Issue permission? Being admin does not mean you are able to do everything if you deny the permission to yourself.

[Children Services IT]

HI, My name is David. Bonita is my manager. I am the tech assisting with this. We have the newest version of Jira and Confluence on a test environment with developer license. I have given it to the developers to test and one of the issues is when they create a project and create issues in it, they can't delete the issues but they can delete the whole project.

The permission scheme does have delete allowed. Is there anything else I need to check?

Log's referral number: 46ce814c-7961-48b9-aaa0-80837f574043

Cause

Referer URL: http://itdjira.csd.toronto.ca/secure/RapidBoard.jspa?rapidView=5&projectKey=QAAC&view=detail&selectedIssue=QAAC-18

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

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:180) [?:?]

     at com.atlassian.greenhopper.service.lexorank.LexoRankOperation.execute(LexoRankOperation.java:119) [?:?]

     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) [classes/:?]

     at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper$DeletedIssueEventData.collectCustomFieldValues(DefaultIssueDeleteHelper.java:288) [classes/:?]

     at com.atlassian.jira

[Andy Heinzer]

Hi Dave and Bonita,

This error means that there is a problem in regards to the lexoranking in Jira.  There should be exactly 2 markers for this ranking, but all we know right now is that your data does not have exactly 2.

I would recommend following the KB Cannot reindex jira due to Expected exactly 2 rows the maximum marker row and the lowest ranked row for rank field, in order to further diagnose the problem here.   It could be that you have multiple rank fields, and perhaps one of these is obsolete, or it could be you have 3 or more marker, or you're missing at least 1.   If you are not in the process of doing an XML restore or Jira upgrade here, then root cause #1 probably won't apply here.

What database are you using for Jira?  If this is postgres, then you could run the following SQL query to better understand what markers you might have in your database:

SELECT
  "FIELD_ID",
  "TYPE",
  substring("RANK" FROM 1 FOR 1) AS bucket
FROM "AO_60DB71_LEXORANK"
WHERE "TYPE" IN (0, 2);

From that KB:

This query should return you two rows for each Lexorank custom field, one with TYPE = 0 (minimum ranked row) and one with TYPE = 2 (maximum marker). 
e.g. if you have 2 Lexorank custom fields, then the queries should return you four rows. 
They should also be in the same bucket if balancing is already completed. If you have more than 2 rows returned per custom field, there may be a serious corruption on the LexoRank table.

I would also be interested to learn if you can run this SQL query as well:

SELECT propertyvalue
FROM propertyentry
  LEFT JOIN propertynumber ON propertyentry.ID = propertynumber.ID
WHERE property_key = 'GreenHopper.LexoRank.Default.customfield.id';

This will tell us the specific field id of your ranking field.  I can see the error message references field id 10005, but I'd like to confirm this via this SQL query, as it is possible you might have multiple ranking fields.

With these two SQL results, we should be able to then advise you as to the next steps to take to try to resolve this problem.

Andy