Order of created tasks for product backlog item

Edit Subject

Tasks should be default ranked in the order they are entered.

Currently I enter tasks for a user story in the order we've ranked them, but UT adjusts the rank so the first task entered for a user story is ranked the lowest. This forces me to re-rank all user story tasks after they are originally entered.

This reply was created from a merged topic originally titled
Tasks should be default ranked in the order they are entered.

When ordering tasks in Planning or Task Board default to ordering by ID. I have removed the Backlog Priority field from the task item, but since tasks tend to get created in a natural order with increasing IDs, the implicit ordering by ID is sufficient for a reasonable, simple ordering.

This reply was created from a merged topic originally titled
Default to ordering Tasks by ID.

Sounds fine! But what if you order the priority of tasks and then later add a new one? Or are you saying that prioritizing tasks is not there anymore..?

John said he removed the Backlog Prio field from the task. If I read correctly this means that the ordering now is by ID which is ascending. So tasks will be ordered in 'natural' order.

But, what happens:
- if I change the parent of the task (move task from one to another backlog item)
- if I add a new task after I reordered tasks (so I created a task which initially appears at the bottom, then I moved it to another position and I create a new task again -> will it be placed below the previously created task?)

Reordering tasks happens frequently here, if the ordering is just by ID I foresee all kinds of unexpected behavior (but I guess I did not get it completely)

Regards,

Rob

Ordering is as follows: Priority field (ascending) and Id (descending). This is to ensure that new work items always appear on top making them easy to find.

If you remove the priority field from your work item definition, you will not be able to rank/prioritize them anymore using the drag and drop feature. For example, the Impediment work item type in the Scrum 1.0 process template doesn't have a priority field. It can only be moved to another iteration/area but it cannot be reordered.

Now I understand that it would be preferable for tasks to be ordered naturally, in the order in which there were created. This is already on our backlog.

Louis, that is correct. But, in case you reorder the priority manually.. then the next item to be added should also come 'naturally' as last item.

Just created a new backlog and had to manually reorder all of my tasks for all stories I was working on.

I hope something can be done in the next release..?

hahaha! and I've always been more of a cat person!

Truth is, this was already planned for the next release. We will fill in the priority field when opening the work item editor with the priority of the last child item, plus some offset.

Sorry we had to make you beg! :)

En garde!



:-)))

Solution sounds good, thanks!

Great news! Thanks!