Why is my issue card not allowing me to move it up/down in the to do column for 2 specific cards?

Question

Hi there,

here's a headscratcher  (at least for me as i try to replicated it)
Never happened before on this board not sure what changed.

Project is a SCRUM project template, Team Managed- and I'm on the "board view"
As my Sprint progresses, I re-prioritize the cards up or down.
I have (2) cards that do not want to move up or down, so I've worked around it by re-stacking everything else in the to-do column (which is a short term fine work around)

My question is, why these 2 specific ones, did i set a setting off?
Both are task type issues, one was created Oct 25th the other created Nov 8th. 
One is lowest priority the other is high priority.
Both are assigned to the same person, and I'm the reporter for both.

I troubleshooted by creating new issues cards and assigned to myself to test re-ordering them in the column while on the board view (couldn't replicate)
I also tried to add 1 more for the same developer as a test (couldn't replicate)

I am able to successful re-order them while on the backlog view or by moving all the other cards queued up.

Curious if this is an odd glitch? Or if anyone's come across this before, and what setting needs to change.

Thanks so much!

Nic Brough -Adaptavist- · Answer

Oh, I see, you're looking at ranking, not status.

To enable ranking, your board filter must be ordered by rank and nothing else.

Mary Henin · Answer

just wanted to help clarify, i'm not trying to "move a card from one status to another when status are in the same column"
I'm trying to either :
1) Move the card up/down the column to organize cards based on priority for each team member. 
2) Move the card physically from one column to the next as it progresses, which is fundamentally what one does on Kanban boards

I just get a red circle with a line through it, like a "do not enter"

Mary Henin · Answer

Thanks so much for your note @Nic Brough -Adaptavist-
It seems that its a recent update. I've been on Jira for 1+ years now, and my team for more than me, and this flair up has been quite recent in the past couple weeks. 
Not sure if there are new paraments or something that's changed in a recent release software update that is causing this.