I'm using Jira 6.2.5 with Jira Agile 184.108.40.206
When trying to rank issues on a kanban or scrum board, I receive the error below. This occurs on all issues and all boards.
"JIRA Agile cannot execute the rank operation at this time. Other users may be ranking the issues that you are trying to rank. Please try again later."
I found an article that suggested turning on validation-query in the ocnfiguration file and also checking database table AO_60DB71_ISSUERANKINGLOG for any unprocessed records. Neither of these 2 suggestions resolved the issue.
There is nothing written to any log file when this occurs.
I can't say for sure if this is what caused the problem or not, but it looks like the upgrade from Jira Agile v220.127.116.11 to v18.104.22.168 performed some upgrade tasks migrating the original Rank field to something called a LexoRank field.
"Starting upgrade task (buildNumber=44) : Migrate to LexoRank field"
Has anyone else encountered this and have a solution?
Im having the same issue on my onDemand intance . Just started using it two days back and started importing issues into my instace from Mantis. Now that they are there when i drag things from the backlog into the sprint i get these errors as well as just simple reording
i hope someone at jira reads this thread. it is a shame to get money from customers for support but when you submit a ticket you are referednto use this forum although answers can only given from some internal jira experts.
we use the java api and ranklast works fine and with rankfirst i get same error as others report here.
if this is the strategy for atlassian than i wonder how the future looks like. jira is a tool companies depend on and if it does not work it can have significant impact. i hope some support manager react on this and change the support policies. as we see nobody helped the customers on this problem.
There is aknown bug reported and being worked on with high priority that I believe addresses your problem. Here is the link: https://jira.atlassian.com/browse/GHS-10872
There is a statement from the developers there as well.
I hope this can give you some light. Please note that there are some workarounds described there as well, so you could take a look to check if they work for you.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs