{"id":47098,"date":"2024-09-17T02:19:52","date_gmt":"2024-09-17T02:19:52","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=47098"},"modified":"2024-09-17T02:20:07","modified_gmt":"2024-09-17T02:20:07","slug":"azure-devops-system-process-inherited-processes","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/azure-devops-system-process-inherited-processes\/","title":{"rendered":"Azure DevOps: System Process & Inherited Processes & Add New Field"},"content":{"rendered":"\n

Comparison between System Processes<\/strong> and Inherited Processes<\/strong><\/h2>\n\n\n\n

Here is a comparison between System Processes<\/strong> and Inherited Processes<\/strong> in Azure DevOps in a tabular format:<\/p>\n\n\n\n

Aspect<\/strong><\/th>System Process<\/strong><\/th>Inherited Process<\/strong><\/th><\/tr><\/thead>
Definition<\/strong><\/td>Default process templates provided by Azure DevOps, like Agile, Scrum, or CMMI.<\/td>Customized versions of system processes created by users to fit specific project needs.<\/td><\/tr>
Customization<\/strong><\/td>Cannot be customized directly. Fields, states, and workflows are fixed.<\/td>Fully customizable. You can add custom fields, states, rules, and workflows.<\/td><\/tr>
Examples<\/strong><\/td>Agile, Scrum, CMMI (default templates).<\/td>Custom Agile, Custom Scrum (inherited versions).<\/td><\/tr>
Creation<\/strong><\/td>Created by Azure DevOps and applied by default.<\/td>Created by users by inheriting from a system process.<\/td><\/tr>
Modifying Work Items<\/strong><\/td>No modifications allowed.<\/td>Allows modifications such as adding custom fields, workflows, and layout changes.<\/td><\/tr>
Control over Fields<\/strong><\/td>Pre-defined fields only.<\/td>Can add, edit, or remove fields based on project requirements.<\/td><\/tr>
Control over States\/Workflows<\/strong><\/td>Pre-defined states and workflows.<\/td>Can modify states (e.g., adding new states) and workflows for custom requirements.<\/td><\/tr>
Assigning to Projects<\/strong><\/td>Assigned by default when creating new projects unless otherwise specified.<\/td>Must be manually assigned to a project after creation.<\/td><\/tr>
Suitability<\/strong><\/td>Suitable for standard workflows without customization needs.<\/td>Ideal for organizations needing customization for specific project workflows.<\/td><\/tr>
Versioning<\/strong><\/td>System processes are maintained and updated by Microsoft, and updates are applied automatically.<\/td>Inherited processes are maintained by the user, and they won\u2019t receive updates unless modified manually.<\/td><\/tr>
Security\/Permissions<\/strong><\/td>Default system permissions.<\/td>Permissions and rules can be adjusted for custom processes.<\/td><\/tr>
Typical Use Case<\/strong><\/td>Teams that follow industry-standard methodologies like Agile, Scrum, or CMMI.<\/td>Teams that need specific modifications to standard methodologies.<\/td><\/tr>
Upgrade Path<\/strong><\/td>Cannot be upgraded or changed directly.<\/td>Inherited processes can be modified as project needs evolve.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Key Takeaway:<\/h3>\n\n\n\n
    \n
  • System Processes<\/strong> are rigid and predefined, ideal for teams that do not need any customizations.<\/li>\n\n\n\n
  • Inherited Processes<\/strong> are flexible and customizable, allowing teams to tailor the process to their specific needs.<\/li>\n<\/ul>\n\n\n\n

    Steps to Enable Custom Fields in Azure DevOps:<\/h2>\n\n\n\n

    The ability to add custom fields is disabled in Azure DevOps<\/strong>, it is likely because your project is using a System Process<\/strong> (like Agile, Scrum, or CMMI), and you cannot modify system processes directly. Azure DevOps only allows you to customize work items in Inherited Processes<\/strong>.<\/p>\n\n\n\n

    Here\u2019s how you can enable customization by creating an Inherited Process<\/strong>:<\/p>\n\n\n\n

    Steps to Enable Custom Fields in Azure DevOps:<\/h3>\n\n\n\n
      \n
    1. Go to Organization Settings<\/strong>:\n
        \n
      • Navigate to your Azure DevOps<\/strong> organization, and in the top-right corner, click on the user icon and select Organization settings<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
      • Navigate to Process<\/strong>:\n
          \n
        • In the Settings<\/strong> menu on the left-hand side, under the Boards<\/strong> section, click on Process<\/strong>.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • Create an Inherited Process<\/strong>:\n
            \n
          • Find the process that your project is using (for example, Agile<\/strong>, Scrum<\/strong>, or CMMI<\/strong>).<\/li>\n\n\n\n
          • Click the three dots (...<\/code>) next to the process and select Create inherited process<\/strong>.<\/li>\n\n\n\n
          • Name your inherited process and save it.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
          • Assign the Inherited Process to Your Project<\/strong>:\n
              \n
            • After creating the inherited process, go to the Project Settings<\/strong> of your project.<\/li>\n\n\n\n
            • Click on Boards<\/strong> > Project configuration<\/strong>.<\/li>\n\n\n\n
            • Find the section that allows you to change the process and assign your project to the newly created inherited process.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
            • Add Custom Fields<\/strong>:\n
                \n
              • Once your project is associated with the inherited process, go back to Organization Settings<\/strong> > Processes<\/strong>.<\/li>\n\n\n\n
              • Click on the inherited process, then navigate to the Work Item Types<\/strong> where you can now add custom fields by following the steps outlined earlier.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                By creating an Inherited Process<\/strong>, you’ll be able to unlock the customization options, including adding custom fields, modifying work item forms, and tailoring the process to fit your project’s needs.<\/p>\n\n\n\n

                \"\"<\/figure>\n\n\n\n
                \"\"<\/figure>\n\n\n\n
                \"\"<\/figure>\n\n\n\n
                \"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"

                Comparison between System Processes and Inherited Processes Here is a comparison between System Processes and Inherited Processes in Azure DevOps in a tabular format: Aspect System Process… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-47098","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/47098","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=47098"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/47098\/revisions"}],"predecessor-version":[{"id":47104,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/47098\/revisions\/47104"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=47098"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=47098"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=47098"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}