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

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

Unable to drag & drop issues (prioritize) within backlog : Internal server error

Within the backlog I cannot drag & drop issues. If I want to do this I receive an error: 

"Issue DUM-83 couldn't be moved. Internal server error" 


The task/issue goes back to its original position: ranked by number. 


7 answers

Hi guys,

I found a workaround for this problem. Since the "rank" is empty for new cards, the solution I found is to modify the board's filter query, replacing the RANK by another field.

Current: project = JA ORDER BY Rank ASC


Daniel Ebers Community Leader Jul 11, 2021

Yes, that fixes it but to the price that ranking will be impossible, I strongly guess.
Have you checked LexoRank troubleshooting page if it is able to spot any problem by integrity check?

You can find it here:

I did the integrity check, and that was the error I found:

Captura de Tela 2021-07-12 às 12.46.09.png

Seems like we're affected by this as well. Was working fine last week. Is there a solution/fix for this issue?

Daniel Ebers Community Leader Jul 11, 2021

It is hard to pinpoint a potential root cause from the outside but at least I can share there is a troubleshooing page including an integrity check in your instance - you could execute it.

In case you are not on a Free-plan in cloud you also could raise a request with Atlassian Support to let them double check.

replied to wrong thread ...

This just popped up for me, new tickets are being created without a Rank. Was working fine yesterday and prior, just started happening today. Has anyone identified the cause or solution?

Daniel Ebers Community Leader Jul 11, 2021

Has this been resolved for you meanwhile? If not, below I posted a link to ranking troubleshooting page which you could use - also letting Atlassian support about it could be an alternative.

yes, thank you Daniel ... we identified the cause was due to a poorly performed import that essentially corrupted jira's db, required atlassian support to delete duplicate items. IIRC Lexo Rank was a tool that helped us identify that there were duplicates.

Did you ever get this figured out? I'm running into the same issue

No, not yet. 

Any ideas or suggestions are still welcome...

Daniel Ebers Community Leader Feb 11, 2021

@Aj.J.Longare you by any chance on a different plan than the "Free" one and could let Atlassian know about this per a support request?

It seems the problem is persisting for Ineke but as her team is on a Free plan she cannot open a request with Atlassian.

Please do let me know.
From looking at the history of it I am not convinced we will get it sorted out by Community help only.

@Ineke Strobbe @Daniel Ebers I did a little digging and the issue seemed to be related to the "Rank" issue field. For some reason, several of the issues we created did not receive a rank when they were created and this prevented moving them in the backlog. We've updated the field for each issue and are now able to position them within the backlog. I'm still not sure why they didn't receive a rank initially.

Daniel Ebers Community Leader Feb 11, 2021

@Aj.J.LongVery good finding! I can imagine that there is a relationship to the trouble you are facing because the field is tightly related to ranking.

Just a question for a better understanding - did you update the rank field programmatically of some kind?
In Issue Navigator I am able to locate the field (via columns) but I am wondering what you put in there.
The fomat is kind of "0|i000lr:" and so on ... did you sort manually across all values or did you update it like "123".

In the former - how did you figure out what to put in?

Thanks in advance!

0 votes
Daniel Ebers Community Leader Jan 09, 2021

Hi @Ineke Strobbe

is there the possibility to get a slightly bigger screenshot with some context around in order to see from and to where you are trying to move the cards?
Please also describe what you are trying to do with the card exactly so Community is better able to understand - especially if providing a screenshot is not suitable.

Apart from that the error message should be presented in a way it tells what is wrong. The generic info "internal server error" is less useful.


0 votes

the "internal server error" is a bit concerning however, be sure you have the necessary permissions - schedule issues, edit issues, etc

Hi @Jack Brickey 

All the issue permissions are assigned. 

Even the org & site admin user has the same problem: the internal server error.

Jack Brickey Community Leader Jan 08, 2021

Hi Ineke,

I need to back up here a bit. So are you talking about moving issues w/in the Backlog screen where you can drag/drop to "Rank" them or are you talking about moving an issue w/in the board from column to column? The reason I'm asking is that your OP seems to convey w/in backlog (ranking) but your images are of the board config.

Hi @Jack Brickey 

I'm talking about moving issue within the backlog screen: selecting one or more issues and drog and drop them in order to rank the issues. 


An example:

I select issue DUM-14 and drag it to the top of the list. 


The moment that I release: I get the error message and the issue has been placed back in the list, ranked by the issue number. 



0 votes

Hi @Ineke Strobbe ,



Check Board filter , ranking is enabled or not 

project = ABC ORDER BY Rank ASC



Go to Board.

Board settings 


Tag the statuses in columns with workflow statuses.




Thanks for your feedback. But both look ok I think. See images below.






May i Know the what is the Workflow status of "DUM-83".

All issues have the workflow status 'Backlog' at this moment.

you using Classic Scrum or Kanban.

Please go to board

Board settings


Under TO-DO Column add Ready for  ... along with Backlog

and remove  the column "Ready ..."


We are using indeed Scrum board

We want to keep the seperate column "Ready for development", but in order to test what you suggested I followed your instructions. See the new situation:

But the problem and error message still exist when I try to prioritize the issues.


It's really weird one. Me also clueless. Sorry 

@Ineke Strobbe 

Can you try to create a new scrum board and try once with the default setup , don't customize columns and statuses , for the last time try once 

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Apps & Integrations

🍻🍂Apptoberfest Update: Upcoming Virtual Events 🎉

Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...

140 views 1 12
Read article

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