Can't drag and drop subtask tickets / tickets locked in place

[Edgars]

Hello.

I have the following situation in Kanban board:

• I have created and assigned regular tasks
• 4 separate subtasks
• out of 4 subtasks, 2 are related to the same parent ticket

And now I have the following issues:

1. I can't move (drag and drop) any of the subtasks in Kanban board
2. I can't move a regular ticket in between subtasks - to set priority/sequence which ticket should be handled first
3. I can't split (drag and drop separately) two of the related tasks either e.g. if I would need one to be done earlier than the other one + add some other tickets in between the two

Please see the attached photo for more info.

Thank you in advance for your help!

P.S. tasks seen in the photo are in To Do status, parent tickets for the subtasks are in Done status if that matters.

[Marcela Junyent · Accepted solution]

Hi! Do you have the board query order by rank?

Board - Configuration - Ranking (Image attached)

Regards, Marce

[Edgars]

@Marcela Junyent indeed I do. So that ranking part is the issue here and if removed should be working fine?

[Marcela Junyent]

No, It has to be order by rank to allow drag and drop.

The other thing to verify is permition scheme.

Do you have schedule and edit permitions?

Also check the column -status mapping.

[Edgars]

I have permissions to schedule and edit - tickets seen in my screenshot were created by me.

Also, I can change columns on the board from where the screenshot was taken.

[Marcela Junyent]

I would need more information. Can you send me the same image that I send you of your board. Because the only way in  which I could replicate your problem was with my first answer.

regards, Marce

[Edgars]

[Marcela Junyent]

Hi! I think that the problem is related to this to concepts:

• When you rank an issue that has sub-tasks, all of the sub-tasks are automatically moved with the issue.
• Sub-task issues can only be ranked in relation to their 'sibling' issues.

you can check ranking behavoir in: 

https://confluence.atlassian.com/jirasoftwareserver084/ranking-an-issue-979407604.html

[Edgars]

@Marcela Junyent thank you for the explanation, I think I got the idea.

Also now tried the following case:

1. assigned parent ticket to the same person who is dealing with subtasks
2. changes status of the parent ticket to the same one as subtask(s)
3. now I can move the whole batch (parent ticket + subtask(s)) in the board

I would assume this is the only way than to move the subtasks around the board = keep parent ticket in the same status / assigned to the same person?

Even though that's not a very convenient solution e.g. if I have a parent ticket with multiple sub-tasks which must be assigned to multiple people -> that would make me reassign the parent ticket every time I would like to amend subtask priority in each person's board... in other words, it would be easier for me to create a simple ticket and add a reference to the parent ticket instead of doing all the above :(

[Marcela Junyent]

Hi! I don't agree with the assumption, subtask has its own issue key and can be moved through boards independently. 
But this topic can help you with your analysis:

https://community.atlassian.com/t5/Jira-questions/When-should-you-create-a-subtask/qaq-p/61350

I hope it helps! 

Marce

[Edgars]

@Marcela Junyent based on the provided information and the article link I read that Jira intends that Parent ticket is moving along the way with subtasks and subtasks are intended to be just a breakdown of a Parent ticket.

Yet in my case I have a need to use Parent ticket as the initial point of discussion, scoping, and subtasks as actual implementation.

Plus there is a constant need to assign tasks/subtasks to various developers and/or with various deadlines, which leads to a situation where Parent ticket will be long done or say pending in status "ready/in progress" while subtasks will be assigned to multiple people and constantly changing statuses which at this point can't be achieved as in such case I get Kanban board with locked in place subtasks (as described before).

Maybe it is just me using subtasks not as they were intended in Jira...

[Marcela Junyent]

I agree with your conclusion. Subtask should be simple technical task. They are not part of the backlog by themselves. May be you should use epics with tasks and stories in it.

Regards, Marce

[Edgars]

Appreciate all the help @Marcela Junyent !

[Marcela Junyent]

your wellcome!!