Share
ReportI've got a flow that triggers from an update to an Azure DevOps update - if a tag is added to a work item, create a child work item. That part works perfectly, but the problem lies in the way I built the flow, and its results.
I don't know of a way to trigger a flow from the tag addition, so I look for the "When a work item is updated" trigger, and add a condition that specifies the tag I specify. Then I have a Yes/No flow: the Yes flow creates a child work item:
Link URL: dynamic content - [URL] The URL of the work item
Link Type: Hierarchy-reverse
That part works beautifully.
I thought I could add another step, so I don't keep adding child items any time the parent item is updated... which is to remove the tag, so no more updates create more child items (I will constantly update work items, and don't want a million duplicate children created as a result).
I don't think there's a way to remove an ADO tag with Power Automate, so I thought about a custom field - how about we trigger from the field update from the parent work item, create the child, then reset the parent work item's field so future updates don't trigger the flow?
That sounded fantastic, but I can't get the "if YES" flow to reference the original work item, instead of the newly-created child.
Advice?
All responses (
Answers (
8,705
