How to properly add or manage a repeated User Story in Auzre DevOps's backlog?
Alberto last edited by
A user story needs to happen each sprint, and I want it to handle it properly - whatever that may mean - within Azure DevOps. I am used to adding user stories for single-issue tickets but have never before had to do a ticket that gets repeated. Is it as simple as adding a new single-issue ticket every sprint, or can I set it up automatically?
These some some articles I came across while using Auzre DevOps's backlog. I hope it helps: https://docs.microsoft.com/en-us/azure/devops/boards/work-items/guidance/agile-process-workflow?view=azure-devops https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/add-work-items?view=azure-devops&tabs=browser https://docs.microsoft.com/en-us/azure/devops/boards/backlogs/bulk-modify-work-items?view=azure-devops