Due to the fact that tasks from a user story are being added simultaneously it leads to race conditions and causes the order of the tasks in Azure DevOps to be semi-random after they are published.
Idea: add tasks in a sequential way to keep the order. It will take longer to publish, but it will keep the correct order.
ipatalas
commented
3 years ago
Due to the fact that tasks from a user story are being added simultaneously it leads to race conditions and causes the order of the tasks in Azure DevOps to be semi-random after they are published.
Idea: add tasks in a sequential way to keep the order. It will take longer to publish, but it will keep the correct order.