cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
saigkill Advocate I
Advocate I

Forwarding GitHub Issue to Azure DevOps

Hello,

currently i'm trying to build a Flow which forwards a GitHub Issue from a special GitHub Repository to the development Repository on Azure DevOps.

It exists a "Create work item" task, but the trigger "If a new problem is opened or assigned" doesn't contains a Source Repository, where the Flow should see.

Exists another option to build my Flow?

Greetings

Sascha

3 REPLIES 3
Community Support
Community Support

Re: Forwarding GitHub Issue to Azure DevOps

Hi @saigkill,

 

I did a quick test on my side, and the trigger you mentioned is really unable to specify a repository.

Perhaps you could consider configuring Condition to determine whether the Repository_Url is the specified url of the source repository, and then configure following action.

In addition, If you want the trigger you mentioned to be able to specify Source Repository, please consider submitting an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

 

Best Regards,

Barry

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
saigkill Advocate I
Advocate I

Re: Forwarding GitHub Issue to Azure DevOps

Hi @v-bacao-msft,

i added the idea to your mentioned feature request tracker.

For now i could try to use your idea with adding a condition. How can i do this? The settings only provide a option to set a TrackingID, Repeating Rule and Paralellism.

Greetings Sascha

Akelitz
New Member

Re: Forwarding GitHub Issue to Azure DevOps

Hi @saigkill.

Add a new Condition step right after the GitHub step.

Select the GitHub Repository Url, "is equal to" or "contains" as condition and the URL of the relevant repository matching value. In advanced mode it should look similar to "@contains(triggerBody()?['repository_url'], 'YOUR REPO URL')".

You can ignore the "If no" branch and add the step to create the work item in Azure DevOps in the the "If yes" branch.

It should work.

Cheers Giorgio.

Helpful resources

Announcements
firstImage

New Ranks and Rank Icons released on April 21!

The time has come: We are finally able to share more details on the brand-new ranks coming to the Power Automate Community!

firstImage

Now Live: Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Community Summit North America

The top training and networking event across the globe for Microsoft Business Applications

Top Solution Authors
Users online (6,218)