Next select the Project Name from the Project Name drop down ( ProjectName). In the next window, choose your organization’s Account name from the available Account Name drop down ( ). Select +Create and select new Automated flow.Ĭhoose trigger for Azure DevOps by searching for Azure DevOps and select When a work item is created and click Create. Now that you have created that field on the User Story Work Item, navigate to Microsoft Flow.
This will allow you to indicate on a User Story that the tasks were automatically created, thereby ensuring you do not create duplicate tasks for that story (more on that later). Select the Work Item “User Story” and create a new field called Tasks Created with a Type of Date/Time. Once you have an account with Administrative privileges navigate to your Azure DevOps instance and customize the current process for your Project. You will need Administrative privileges in order to make changes to your Project in Azure DevOps. Instead of tasking the team with creating the same tasks repeatedly for each created User Story, Product Backlog Item (PBI), we can create a Flow to automate this work. Consider a situation where you typically have the same 9 tasks across your development teams for most but not all User Stories (more on that later). Let's say your team is tasked with ensuring that the team follows a common process when developing, testing, and releasing work. Microsoft Flow can help! By connecting Microsoft Flow to your Azure DevOps account and following the steps below, you can automate Task creation for “common or repetitive tasks.” Check it out… Agile teams who use Azure DevOps face a challenge: creating Tasks can take time away from the Dev team, depleting capacity that would be better spent developing. One application is to automatically create Work Items in Azure DevOps (Previously known as VSTS Online or Visual Studio Team Services Online). Microsoft Flow is a powerful tool with many different applications and possibilities.
0 kommentar(er)
