Power Platform Community Forum Thread Details

the story is alreay created in the Azure Devops board with the acceptance criteria and details. How to add the tasks on to the story at the begining of the sprint?

Categories:

Connector development

Hi @SM-24042110-0,

Creating Child Tasks in Azure DevOps using Power Automate
To automatically create multiple tasks and link them to an existing User Story, you cannot rely on a simple Parent field. In Azure DevOps, parent child relationships are managed through work item links.

Recommended workflow
1. Trigger
Use a manual trigger, a scheduled trigger, or the “When a work item is created or updated” trigger filtered to User Story.

2. Create the task
Use the Create a work item action.
Set the work item type to Task and provide a task title such as “QA Testing”.
Tip: Map the Area Path and Iteration Path from the User Story so the task stays in the same sprint.

3. Link the task to the User Story
Right after creating the task, add an Update a work item action.
Use the task ID returned from the create step.
Select Hierarchy Reverse as the link type, which represents the child relationship.
Provide the User Story ID as the linked work item.

Why this step matters
Azure DevOps stores relationships separately from standard fields like title or description. Adding the link explicitly ensures the task appears correctly under the User Story on the sprint backlog and task board.

Creating multiple tasks
If every User Story follows a standard checklist such as Design, Development, and QA, store these task names in an array variable. Wrap the Create and Update actions in an Apply to each loop so all tasks are generated automatically when a story is ready.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/