Menu
With Azure DevOps Server 2019 RC it is possible to enable inherited process model on new collections (see release notes). Is there any way to use the inherited process model also for existing collections, where no customization on the process was made
325
This article applies to Azure DevOps Services and Azure DevOps Server 2019 and later versions. To customize any project defined on a collection for TFS 2018 or earlier, see On-premises XML process model. You can only use the Inheritance process model for projects defined on a project collection configured to support the Inheritance process model.
For Azure DevOps Server 2019 and later versions, you have a choice of process models. When you create a project collection, you'll need to choose between On-premises XML process model and Inheritance process model. To learn more, see Customize work tracking, Choose the process model for your project collection.
Azure Boards | Azure DevOps Server 2020 | Azure DevOps Server 2019 To customize the work tracking system, you customizean inherited process through the administrative user interface for the organization. All projects that use an inherited process get the customizations made to that process.
Create and manage inherited processes 1 Prerequisites. ... 2 Open Settings>Process. ... 3 Create an inherited process. ... 4 Change the process used by a project. ... 5 Create a project from a process. ... 6 Copy a process. ... 7 Enable/disable a process. ... 8 Set the default process. ... 9 Try this next
Inherited process model is currently only supported for new collections created with Azure DevOps Server 2019 and not for existing collections.
See this Developer Community entry which asks for it.
175
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
