Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Delete issue failed

Hello Support,

we are not able to delete any issue in our JIRA and sorting in Backlog also not able.

We have installed some Plug-Ins like BigPicture, R4J, T4J, ...

And we also moved the jira server from an further instance with the import function at installation guide.

I also checked the "Global Rank". But that`s not the problem. 

 

Drücken Sie auf Löschen oder die Rücktaste, um diese Option zu entfernen.

Entschuldigung, wir hatten technische Probleme während ihrer letzten Aktion.

Fordern sie Unterstützung an

Kopieren sie den Inhalt unten und senden sie ihn an ihren Jira Administrator

Technische Details

Verweisnummer des Protokolls: 875001a0-8ccf-4392-9dc6-738da0ae3f2c

Ursache

Verweiser-URL: http://10.13.6.36:8080/secure/RapidBoard.jspa?rapidView=8&view=planning&selectedIssue=PCMK-35

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:165) [?:?]
	at com.atlassian.greenhopper.service.lexorank.LexoRankOperation.execute(LexoRankOperation.java:114) [?:?]
	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.issue.managers.DefaultIssueDeleteHelper$DeletedIssueEventData.<init>(DefaultIssueDeleteHelper.java:275) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueDeleteHelper.deleteIssue(DefaultIssueDeleteHelper.java:120) [classes/:?]
	at com.atlassian.jira.issue.managers.DefaultIssueManager.deleteIssue(DefaultIssueManager.java:723) [classes/:?]
	at com.atlassian.jira.issue.managers.RequestCachingIssueManager.deleteIssue(RequestCachingIssueManager.java:232) [classes/:?]
	at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:402) [classes/:?]
	at com.atlassian.jira.bc.issue.DefaultIssueService.delete(DefaultIssueService.java:378) [classes/:?]
	at com.atlassian.jira.web.action.issue.DeleteIssue.doExecute(DeleteIssue.java:23) [classes/:?]
	at webwork.action.ActionSupport.execute(ActionSupport.java:165) [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:63) [jira-api-7.13.0.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) [webwork-1.4-atlassian-30.jar:?]
	at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:225) [webwork-1.4-atlassian-30.jar:?]
	at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:154) [webwork-1.4-atlassian-30.jar:?]
	at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:138) [classes/:?]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) [servlet-api.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [catalina.jar:8.5.32]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:8.5.32]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat-websocket.jar:8.5.32]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:8.5.32]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:8.5.32]
	at com.atlassian.jira.web.filters.JiraLastFilter.lambda$doFilter$0(JiraLastFilter.java:39) [classes/:?]

4 answers

0 votes
Andy Heinzer Atlassian Team Apr 18, 2019

Hi Tobias,

Sorry to hear that you are having this error.  However the stacktrace here does indicate the general cause.  In this case I would recommend walking through the diagnosis steps of the KB: Cannot reindex jira due to Expected exactly 2 rows the maximum marker row and the lowest ranked row for rank field.  This will help us to understand better the current state of your lexorank table in the Jira database.

All we know so far is that this rank field doesn't have exactly two markers.  But until we know more details about this error, we can't provide more steps to take to work past this issue.   Each of the root cause sections tend to have different SQL select statements to run against the Jira SQL database.  With these results we should be better able to help you correct this error so that you can delete or move issues in Jira again.

Regards,

Andy

Hi Andrew,

the sql query from root cause #2 has an empty result. There are no entrys in the lexorank table.

 

The query from root cause #3. Shows the id from the error message id 10005.

We have no further ideas.

 

One important thing! We installed this jira instance with the backup from another instance. May this cause the problem?

0 votes
Andy Heinzer Atlassian Team Apr 30, 2019

Hi Tobias,

It is possible that this import caused an upgrade to happen, and in turn if that upgrade task failed in one or more ways, it could have caused this behavior.  

  1. What version of Jira was the backup taken from? 
  2. What version of Jira was the backup restored to?

Depending on the answer to those questions, it might have been necessary to first upgrade Jira to an intermediate version before going to the latest version to make sure that the needed upgrade tasks can be run against your data.

You could still try to the steps in Resolution #4 here to insert the markers for this rank field manually.  However following this approach would likely give up on any existing rank data you might have had in Jira.   If that is not a concern then you can try the steps in #4 and substitute your rank id field value of 10005 where that example uses the 10900 value.

If the rank data is important here, then we will probably want to first understand the backup/restore steps here and perhaps first try to upgrade that data to another version first.

Andy

Hi Andrew,

backup version was 7.10.2

new server: 7.13.0

 

Steps in Resolution #4 not done, yet.


Other error occured also in our jira: Also in new and imported projects 

- Sorting issues in backlog Error message:

Jira Software kann keine Ränge zuweisen. Dieses Board wurde vor Kurzem für die Verwendung des Rangfeldes konfiguriert. Das System muss neu indiziert werden, bevor Sie Vorgängen einen Rang zuweisen können. Bitten Sie Ihren Administrator, eine manuelle Neuindizierung vorzunehmen.

- Switch issue to another project also not possible. Error Message:

Verweiser-URL: http://10.13.6.36:8080/secure/MoveIssueUpdateWorkflow!default.jspa?id=11064&assignee=null

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

 

Is it possible to have a look via remote at our system?

Andy Heinzer Atlassian Team May 08, 2019

Hi Tobias,

I am afraid our support offerings for Community support do not extend to that level.

However, after translating your message, I am confident that this error has the same cause as the first error. 

You could follow the resolution steps in #4 here to correct this.  After you do that, you would need to start Jira again and reindex in order to be able to rank issues and delete these issues then.

Is there some other concerns with following those steps?  It should help resolve these problems.

Andy

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

3,666 views 5 15
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you