Issues with power automate - Unable to Create a new work item when another work item's state is updated in ADO?

Question

Issues with power automate - Unable to Create a new work item when another work item's state is updated in ADO?

Blatt, Shelley 0

I am using Power Automate to create a new work item on a board, when another work item is updated.

I have tried both the following flows & neither will run successful when the conditions are met.

ADO trigger : When a work item is updated and Action > create a work item
ADO trigger : When a work item is updated and Condition = WI = US and state = Ready for Testing & If yes - create a work item & send http request to ADO.

I think i need low level detail support advising field to complete. Thank you

Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-26T14:05:43.9133333+00:00
Hi Blatt, Shelley

Could you please follow the below steps:

Go to Power Automate -> Click + Create -> Choose Automated Cloud Flow -> Search for When a work item is updated -> Click Create

Configure Trigger: "When a work item is updated" -> Choose:

Organization Name: your ADO org

Project Name: your ADO project

In the trigger section -> Go to Settings -> Trigger condition -> Add below condition: @and( equals(triggerOutputs()?['body/fields/System.WorkItemType'], 'User Story'), equals(triggerOutputs()?['body/fields/System.State'], 'Ready for Testing') )

Now Add an action -> Search for Create a work item -> Fill in:

Organization Name

Project Name

Work Item Type: e.g., Task

Title: use dynamic content like Follow-up on @{triggerOutputs()?['body/fields/System.Title']}

Other required fields: Area Path, Iteration Path — match them to the parent item or set them manually.

Save the flow

Go to Azure DevOps -> Change a User Story's state to Ready for Testing -> Return to Power Automate and check Run History.

Additional References:

https://stackoverflow.com/questions/62907396/power-automate-integration-with-azure-devops-boards-create-a-new-issue-with-pa

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-27T06:50:25.92+00:00

Hi Blatt, Shelley

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Blatt, Shelley 0 Reputation points

2025-06-27T13:16:38.5033333+00:00

Hi, thank you for your help.
This is what i had previous, and I have tweaked some parts but i still cannot make the flow run. I have the trigger of a User Story in the State but still the flow will not run & i am unsure what i may be missing.

Here is my example, please let me know if i have missed anything? I have the condition in settings as advised.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-27T14:11:29.0833333+00:00
Hi Blatt, Shelley

From your first screenshot (trigger config), you are filtering the event too early using fields like:

Type = User Story, Area Path, Iteration Path, Priority = 2

Firstly, modify your trigger to only include Organization and Project and Leave all other fields blank.

Right after the trigger, add a Condition to check:
@and( equals(triggerOutputs()?['body/fields']['System.WorkItemType'], 'User Story'), equals(triggerOutputs()?['body/fields']['System.State'], 'Ready for Testing') )

Then follow the steps which I mentioned as above.

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-30T08:29:24.5433333+00:00

Hi Blatt, Shelley

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Blatt, Shelley 0 Reputation points

2025-06-30T10:11:23.4033333+00:00

Hi, I've taken your advice & the flow will still not run at with the WI = user story in Ready for Testing state. I can't even get it to show on the run history at all. Here's what i have done.
2 fields only completed on the first step & the condition in the settings you have given me.
I have a user story in the state & run the flow manually as its never run successfully before.

Any idea why the power flow still wont work? Thanks
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-30T10:41:37.3733333+00:00

Hi Blatt, Shelley

Since the flow isn’t even appearing in the Run History, that tells us the trigger isn’t firing at all.

The When a work item is updated trigger is event-based, not manual. That means:

You can’t manually run the flow to test it.

It will only run when Azure DevOps sends an update event that matches your trigger.

So, if you click Run manually, nothing will happen, and it won’t show in the run history.

And could you please let me know in the User Story -> Under States -> Is Ready for Testing listed or is it a a custom state added by your team.
Blatt, Shelley 0 Reputation points

2025-06-30T12:18:27.95+00:00

Hi, this is a state in the dropdown view in our project..
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-30T13:09:52.83+00:00
Hi Blatt, Shelley

Thanks for your info. Could you please follow the below steps:

Open trigger card -> click 3 dots -> If you see "azuredevops" connection, it’s correct.

Select both organization name and project name from drop-down, don’t type manually.

In Power Automate -> go to My Flows -> The flow should say “On” -> If not, click and turn it on.

For testing:

Create new flow -> choose When a work item is updated

Leave everything blank except:

Org:

Project:

Add Outlook or Email (V2) action:

"Send me an email"

Subject: Work item: @{triggerOutputs()?['body/fields/System.Title']}

Update a User Story and see if the email arrives and wait for 30 - 60 seconds -> check run history.

Go to Connections in Power Automate -> Azure DevOps connection -> Click Fix connection (if available), or reauthenticate it manually.

Additional References:

https://learn.microsoft.com/en-us/power-automate/triggers-troubleshoot?tabs=new-designer

Hope this helps!

Please Let me know if you have any queries.

2 answers

Your answer

Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-26T14:05:43.9133333+00:00

Hi Blatt, Shelley

Could you please follow the below steps:

Go to Power Automate -> Click + Create -> Choose Automated Cloud Flow -> Search for When a work item is updated -> Click Create

Configure Trigger: "When a work item is updated" -> Choose:

Organization Name: your ADO org

Project Name: your ADO project

In the trigger section -> Go to Settings -> Trigger condition -> Add below condition: @and( equals(triggerOutputs()?['body/fields/System.WorkItemType'], 'User Story'), equals(triggerOutputs()?['body/fields/System.State'], 'Ready for Testing') )

Now Add an action -> Search for Create a work item -> Fill in:

Organization Name

Project Name

Work Item Type: e.g., Task

Title: use dynamic content like Follow-up on @{triggerOutputs()?['body/fields/System.Title']}

Other required fields: Area Path, Iteration Path — match them to the parent item or set them manually.

Save the flow

Go to Azure DevOps -> Change a User Story's state to Ready for Testing -> Return to Power Automate and check Run History.

Additional References:

https://stackoverflow.com/questions/62907396/power-automate-integration-with-azure-devops-boards-create-a-new-issue-with-pa

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-27T06:50:25.92+00:00

Hi Blatt, Shelley

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Blatt, Shelley 0 Reputation points

2025-06-27T13:16:38.5033333+00:00

Hi, thank you for your help.
This is what i had previous, and I have tweaked some parts but i still cannot make the flow run. I have the trigger of a User Story in the State but still the flow will not run & i am unsure what i may be missing.

Here is my example, please let me know if i have missed anything? I have the condition in settings as advised.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-27T14:11:29.0833333+00:00

Hi Blatt, Shelley

From your first screenshot (trigger config), you are filtering the event too early using fields like:

Type = User Story, Area Path, Iteration Path, Priority = 2

Firstly, modify your trigger to only include Organization and Project and Leave all other fields blank.

Right after the trigger, add a Condition to check:
@and( equals(triggerOutputs()?['body/fields']['System.WorkItemType'], 'User Story'), equals(triggerOutputs()?['body/fields']['System.State'], 'Ready for Testing') )

Then follow the steps which I mentioned as above.

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-30T08:29:24.5433333+00:00

Hi Blatt, Shelley

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Blatt, Shelley 0 Reputation points

2025-06-30T10:11:23.4033333+00:00

Hi, I've taken your advice & the flow will still not run at with the WI = user story in Ready for Testing state. I can't even get it to show on the run history at all. Here's what i have done.
2 fields only completed on the first step & the condition in the settings you have given me.
I have a user story in the state & run the flow manually as its never run successfully before.

Any idea why the power flow still wont work? Thanks
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-30T10:41:37.3733333+00:00

Hi Blatt, Shelley

Since the flow isn’t even appearing in the Run History, that tells us the trigger isn’t firing at all.

The When a work item is updated trigger is event-based, not manual. That means:

You can’t manually run the flow to test it.

It will only run when Azure DevOps sends an update event that matches your trigger.

So, if you click Run manually, nothing will happen, and it won’t show in the run history.

And could you please let me know in the User Story -> Under States -> Is Ready for Testing listed or is it a a custom state added by your team.
Blatt, Shelley 0 Reputation points

2025-06-30T12:18:27.95+00:00

Hi, this is a state in the dropdown view in our project..
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-06-30T13:09:52.83+00:00

Hi Blatt, Shelley

Thanks for your info. Could you please follow the below steps:

Open trigger card -> click 3 dots -> If you see "azuredevops" connection, it’s correct.

Select both organization name and project name from drop-down, don’t type manually.

In Power Automate -> go to My Flows -> The flow should say “On” -> If not, click and turn it on.

For testing:

Create new flow -> choose When a work item is updated

Leave everything blank except:

Org:

Project:

Add Outlook or Email (V2) action:

"Send me an email"

Subject: Work item: @{triggerOutputs()?['body/fields/System.Title']}

Update a User Story and see if the email arrives and wait for 30 - 60 seconds -> check run history.

Go to Connections in Power Automate -> Azure DevOps connection -> Click Fix connection (if available), or reauthenticate it manually.

Additional References:

https://learn.microsoft.com/en-us/power-automate/triggers-troubleshoot?tabs=new-designer

Hope this helps!

Please Let me know if you have any queries.

Answer 1

Blatt, Shelley 0

Hi, the PA flow of sending an email, when a work item is updated works so proves my ADO & outlook connections are working.

How do i apply this to the flow principle to my flow - when a work item (user story state is updated to 'Ready for Testing', then trigger creation of new work item (task) ?

Answer 2

Durga Reshma Malthi 6,130 Microsoft External Staff Moderator

Hi Blatt, Shelley

I mentioned Ready for testing but as per your work item state it is Ready For Testing (capital F)

Configure Trigger: "When a work item is updated" -> Choose:
- Organization Name: your ADO org
- Project Name: your ADO project
- Leave all filters blank (especially Assigned To, Area Path, etc.)

Click 3 dots on the trigger -> Settings -> Trigger Conditions, and paste:

   @and(
     equals(triggerOutputs()?['body/fields/System.WorkItemType'], 'User Story'),
     equals(triggerOutputs()?['body/fields/System.State'], 'Ready For Testing')
   )

Action: Create a work item -> Type: Task,Title: Follow-up for @{triggerOutputs()?['body/fields/System.Title']},Area Path & Iteration Path: Inherit from the trigger item, Assigned To: Optional and State: New (default)
Save the flow
Go to Azure DevOps -> User Story -> Change its state to Ready for Testing -> Wait for 30-60 seconds
Go back to Power Automate -> Run History -> Confirm it ran and created the Task.

Hope this helps!

Please Let me know if you have any queries.

Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-07-01T08:23:57.62+00:00

Hi Blatt, Shelley

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.
Blatt, Shelley 0 Reputation points

2025-07-01T09:50:22.93+00:00

Sorry the PA Flow still does not work.
The connection on thr PA flow shows ADO with a tick so looks enabled, but the trigger work item in the state ready for testing doesnt seem to be identified & the flow will not run :(
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-07-01T10:38:36.63+00:00
Hi Blatt, Shelley

Could you please follow the below steps once:

Right after the trigger, add the compose action and add below inputs.
{ "WorkItemType": "@{triggerOutputs()?['body/fields/System.WorkItemType']}", "State": "@{triggerOutputs()?['body/fields/System.State']}", "Title": "@{triggerOutputs()?['body/fields/System.Title']}" }
Save and trigger the flow by updating a User Story to “Ready for Testing”

Check the Run History -> Compose output -> this will show the exact string Azure DevOps sends.

If the Compose output shows something like Ready For Testing or ready for testing, update the below condition accordingly.
@and( equals(triggerOutputs()?['body/fields/System.WorkItemType'], 'User Story'), equals(triggerOutputs()?['body/fields/System.State'], 'Ready For Testing') )

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-07-02T09:00:28.4133333+00:00

Hi Blatt, Shelley

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Durga Reshma Malthi 6,130 Reputation points Microsoft External Staff Moderator

2025-07-03T07:59:25.2466667+00:00

Hi Blatt, Shelley

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.

Share via

Issues with power automate - Unable to Create a new work item when another work item's state is updated in ADO?

2 answers

Your answer