Skip to content

Latest commit

 

History

History
167 lines (102 loc) · 10.5 KB

manage-process-templates.md

File metadata and controls

167 lines (102 loc) · 10.5 KB
title titleSuffix description ms.custom ms.service ms.assetid ms.topic ms.author author monikerRange ms.date
Upload, download, or delete a process template
Azure DevOps
Learn how to upload, download, delete, or make default a process template for a project collection in Azure Boards.
work-items, engagement-fy23
azure-devops-boards
5D5AF176-B3C6-47AD-87FF-5FAFE1BA4AAE
how-to
chcomley
chcomley
<= azure-devops
01/05/2023

Upload or download a process template

[!INCLUDE version-lt-eq-azure-devops]

When you create a project, a process is used to specify the work item types to configure and other settings. Each process template primarily defines the building blocks of the work item tracking system for Azure Boards. For the Hosted XML and On-premises XML process models, you can upload a process template to either update an existing project or create a project. For the Inheritance process model, you customize work tracking through the web portal. For more information about these different processes, see Customize your work tracking experience.

::: moniker range="<azure-devops" You can upload and export process templates only for those project collections configured to use the On-premises XML processes. Also, you can mark a template to appear as the default when you add projects.

::: moniker-end

[!INCLUDE version-all]

[!INCLUDE temp]

Prerequisites

To manage process templates, be a member of the Project Collection Administrators group, To get added to this group, see Change project collection-level permissions.

::: moniker range="<=azure-devops"

Important

Uploading and downloading Inherited processes isn't supported. To manage Inherited processes, see About process customization and inherited processes.

[!INCLUDE temp] ::: moniker-end

::: moniker range="azure-devops"

Import a process template (Hosted XML process)

  1. From the Processes tab, choose Import process and then drag-and-drop or browse to the zip file of the process you've customized.

    [!div class="mx-imgBorder"]
    Screenshot of Import Process link.

    [!NOTE]
    If you don't see the Import process link, then your organization isn't set up to support the Hosted XML process model. You should work with the Inheritance process model for your customization needs. The Hosted XML process model is only supported if your account was created through the Data Import Service.

  2. Choose the file to upload. Your custom process must meet specific constraints to pass validation checks during import.

    [!div class="mx-imgBorder"]
    Import Process dialog, choose process file to import.

    Check the Replace existing template if you're updating an existing template. The import process overwrites any template that has the same name as the one you import and requires that you check this box to confirm you want it replaced.

    [!IMPORTANT]
    You can't update one of the locked processes: Agile, Basic, CMMI, and Scrum.

  3. Upon successful import, you'll see the following message.

    [!div class="mx-imgBorder"]
    Import Process success dialog.

    If the process doesn't pass the validation checks performed on import, you'll receive a list of error messages.
    Correct each error and then retry the import.

  4. You can immediately create a project using the newly imported process.

    [!div class="mx-imgBorder"]
    Screenshot of Import process actions menu, Create new team project from imported process.

  5. Complete the form that appears. For more information about the different options, see Create a project.

    [!div class="mx-imgBorder"]
    Dialog for Create new project.

For other Hosted XML process management tasks, see Import and export a Hosted XML process.

::: moniker-end

::: moniker range="<azure-devops"

Manage a process template (On-premises XML process)

  1. To upload a process template, choose the :::image type="icon" source="../../../media/icons/blue-add-icon.png" border="false":::Upload Process Template option.

    [!div class="mx-imgBorder"] Screenshot of web portal, All processes, Upload process template.

    In the Upload process template dialog, choose the .zip folder that contains the root file, ProcessTemplate.xml, for the process template that you want to upload. See also Process template restrictions and validation checks.

    [!div class="mx-imgBorder"] Screenshot of web portal, Upload process template dialog.

  2. To download or export a process template, choose the :::image type="icon" source="../../media/icons/actions-icon.png" border="false"::: actions icon, and choose the Export option.

    [!div class="mx-imgBorder"] Screenshot of web portal, process context menu, Export Process.

  3. To set a process as the default when adding new projects or to disable a process from being used, choose the :::image type="icon" source="../../media/icons/actions-icon.png" border="false"::: actions icon for the process, and select either the Set as default process or Disable process options.

    [!div class="mx-imgBorder"] Screenshot of web portal, process context menu, Disable or Delete a Process.

::: moniker-end

Correlate a process template with an existing project

To determine the type of process template that was used to create your project, review the work item types that appear in the New Work Item menu for Team Explorer and then compare them with the work item types in the following chart. If your work item types differ from those items shown, then a custom process template might have been used.

::: moniker range="<=azure-devops"

Agile Basic CMMI Scrum
Agile work item types Basic work item types CMMI work item types Scrum work item types

::: moniker-end

Process template restrictions and validation checks

If you upload the process template through the web portal, you may come across errors such as those shown in the following image.

[!div class="mx-imgBorder"] Screenshot of Upload process template errors.

Resolve each error and then retry the upload process. You may find additional information about resolving process template errors from Resolve validation errors for process import.

The following validation checks must pass when uploading a process template.

  • Process template names must be unique and 256 Unicode characters or less. Same-named templates overwrite existing templates. Also, names can't contain the following characters: . , ; ' ` : / \ * | ? " & % $ ! + = ( ) [ ] { } < >. For more restrictions, see Naming restrictions.
  • Process template folders can't contain any .exe files. If they do, the process template may upload successfully, however project creation fails.
  • Process template total size should be 2 GB or less, or project creation fails.
  • The upload process runs a partial verification check to make sure that the XML of each process template XML file is valid. If you receive any errors when you try to upload the process template, review the XML to determine the cause of the error. Duplicate tags in an XML file can cause errors. If there's no error in the XML, check to make sure all the appropriate files are included in your process template in the correct folder locations.
  • If XML definition files reference an extension, then the extension must be installed and enabled in the collection.

Important

The schema definition for process templates uses a mix of camel-case and all capitalized elements. If you encounter errors when validating your type definition files, check the case structure of your elements. Also, the case structure of opening and closing tags must match according to the rules for XML syntax. See also Process template plug-ins: Index to XML element definitions.

Related articles

Periodically, updates are made to the process templates to support new features. For more information, see Release Notes for Azure DevOps Server.