nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to change the order of orphaned subtasks in the column

SamLyon

Create a story with a subtask

Move parent to different column

Try to move subtask to a different position in its column, seems to be stuck.

I would like to move a subtask to show priority the only way I have found is by brining the parent back and moving that which seems unwieldy.

adding for clarity:

In Progress col

--task1

--task2

----subtaskOfTask3

QA col

--task3

I want to move subtaskOfTask3 to the top of the col

Accepted answers

All comments

scherbank

I think that is it a process issue. How the sub-task can have higher priority than the master ticket? it should not.

Nic Brough -Adaptavist-

Columns on boards have nothing to do with priority, they are groups of status.

If you can't move an issue from one status to another (i.e. into another column on a board), then the workflow is set up to disallow it.

Have a look at the workflow for the sub-task type, and check what it allows from the current status. If the diagram says there is a transition from the current status into a status in the column you are trying to get it into, then there is a condition on the workflow blocking it.

SamLyon

the master is in another col so it not above it only unrelated tickets

SamLyon

They are groups of statuses, but they are ordered groups. I can change the order of all other ticket types just not subtasks. I can change the order of the subtask if I bring back the parent and move that then take the parent away.

Nic Brough -Adaptavist-

Ah, I think you're talking about "ranking" now, not columns

Ranking sub-tasks outside their parent issue is nonsense, so you can't do it when they've been divorced from the parents.

scherbank

it is not above but it connected logically.

you should manage priority and rank of master only. all sub-tasks are of the same with master priority and rank

SamLyon

ok ignore priority as it is misleading I think. I want to move the orphaned sub task to the top of its column. It works with all other types and the message says it has moved so it feels like a bug.

SamLyon

Don't know the correct word and it probably confuses matters using one as it will clash with a jira field somewhere. I want to move the sub task to the top (or all sub tasks as they are grouped) without brining back the parent. As I said above It looks like a bug.

Jack Brickey

@SamLyon, I want to reset here and restate what I think you are saying and them give my $0.02.

You have a board that is displaying Tasks and some tasks have sub-tasks.
If the sub-tasks are in the same column under the task then you can change the ranking (order) of the sub-tasks. Example: you have T1:S1,S2,S3 then you rerank to T1:S2,S1,S3.
Now you move the task (T1) from say To Do to In Progress but sub-tasks still in To Do.
Next you try to change the ranking (relative relationship of sub-tasks), e.g. back to S1, S2, S3 and you are unable to do so.

Assuming this is an accurate restatement...

The fact that you can do this when the Task is in the same column as the sub-tasks and not when the task is in a different column does seem a bit odd. However as others have noted, sub-tasks should not be ranked independent of the parent. Certainly I see value of ‘ordering’ subtasks under the parent but IMO you should never be able to ‘rank’ them independently of the parent. Example, the following should not be allowed:

Before: T5, T7, T1:S1,S2,S3
After: T5, S2, T7, T1:S1,S3

In the above example the correct process would be to move T1 above T5.

Getting off my soap box and back to your issue and my recommendation - If having them in the same column allows you to achieve your goal you need to stick w/ that for now and you can open a suggestion with Atlassian if you want a different behavior.