How to change the order of orphaned subtasks in the column Edited

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





QA col



I want to move subtaskOfTask3 to the top of the col

3 answers

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

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

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

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.

0 votes

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.

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.

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.

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.

It's not a bug, you're trying to do something that makes no sense.  Ranking sub-tasks outside their parent is nonsense.

so why can I move a task to the top of a col? if its nonsense for one surly its nonsense for all. 

Because tasks are not sub-tasks, and don't have a parent, so they can be ranked against their peers.  The peer group for sub-tasks is "the sub-tasks on this issue", the peer group for tasks is "all other tasks at my level in the backlog"

the group of subtasks is the representation of the task once you move the parent out so you should be able to move them by your logic.

0 votes
Jack Brickey Community Champion Oct 13, 2017

@Sam Lyon, 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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

633 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you