Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Kanban backlog - items jump back to their previous location

Uzi Entin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 8, 2023

hi,

I have a cloud-based Jira Kanban board. I have some sub-tasks which are in the backlog but their parent story/task is already in progress, i.e. the story/task is on the kanaban board while some sub-tasks are still in the backlog. Let's call these Story and sub-tasks: 'Story_A' and 'Subtask_A'.

Now I go into my backlog and start to drag&drop *other* stories around as part of general prioritization and ranking. 

Problem: Whenever I move a story, let's call it 'Story_B' to be just above 'Subtask_A', it will immediately jump back to some random location down the backlog. If I move 'Story_B' above any other story, it will move just fine. But if I try to drag&drop it just above 'Subtask_A', it will always drop down the backlog. 

Thanks in advance for any help.

 

 

1 answer

0 votes
Dave Mathijs
Community Champion
September 8, 2023

Hi @Uzi Entin there may be more causes to this issue.

First of all, cards on your agile board can either be sorted (by a field, ascending or descending) or ranked (manual drag & drop).

Secondly, when your parent issue (e.g. story) is in one status, but your sub-tasks are in another status, the parent issue will be shown in the same column as the sub-tasks on a Kanban Board.

So if you have a sub-task in 'To Do' and another sub-task in 'In Progress', then the parent issue will be shown in both column.

Uzi Entin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 11, 2023

Hi @Dave Mathijs , thank you for the prompt reply.

In my case the board and backlog are sorted based on Rank, so I can indeed use drag & drop to arrange it.

The point with child and parent here, is that the parent is already in a status which is not backlog (does not matter which status sepcifically), while one of the sub-tasks is still in the backlog (and should be there as we didn't start it). It is this specific combination that causes this strange backlog behavior (bug IMHO...).

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events