Using JIRA v8.13.1
There is a JIRA issue in the backlog. A subtask of that issue is in progress status on the board in a column.
The subtask is at the end of many cards in the column.
The subtask couldn't be dragged and dropped in a different location in the same column.
When the card is dragged and dropped somewhere above , the card doesn't move to the new location.
Can the subtask card be reordered ? How ?
The problem is not for just this subtask. It is the same for all subtasks on the board.
I also verified the configuration that the cards on the board is ordered by rank
Hello @Just Another User
The answer is unfortunately no.
The subtask displayed in the board should have a small header above it that identifies its parent issue, like this - SDP-1225 is the parent and SDP-1912 is the subtask
Subtasks can be ranked only relative to the other subtasks under the same parent. Beyond that, they will show in the column in the same position as their parent issue's rank relative to the other story/task/bug issues. You would need to change the rank of the parent issue to change the position of the subtask.
I'm not an expert, but I think the answer is no. Rank is a relative position compared to other issues regardless of status.
If you have issue ranked thus in your backlog:
... then ranking records that Issue-3 has Issue-4 below it and Issue-2 in above it. When the issues change status that rank information remains the same unless you change the issue's rank after changing its status. I don't think I can explain relative ranking adequately or provide a good example that would explain it clearly, but I'll try.
If Issue-3 is changed to In Progress and there are no other issues In Progress, then it will appear to be the highest ranked issue In Progress. But if you then change Issue-2 to In Progress, the relative ranking will automatically put it higher than Issue-3, because that is how the issues were ranked overall.
If you then changed the ranking of those two issues so that Issue-3 was higher than Issue-2, I believe all the affected issues get re-ranked. So then regardless of the status the overall ranking becomes
As you move the issues between statuses, the overall ranking is maintained and that determines their ranking within a given status.
You might use a separate kanban board based on the same filter, but without a backlog screen and with all not-Done statuses mapped to one column.
That would put all your issues into one column where you could re-rank them, and those changes should be reflected in the ranking of issues in your primary board.
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
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