Overview

The Process Templates feature enables teams to define standardized frameworks for product R&D workflows and project delivery workflows based on their business characteristics. With built-in or custom templates, teams can quickly create Products or Projects that match their working model, enabling differentiated process management while improving efficiency and ensuring consistency and compliance in collaboration.

Use Cases

Differentiated process management for software vs. hardware projects: In many organizations, software and hardware projects follow very different workflows. For example, a hardware process template may add a Prototype Build stage, while a software template may not need it.

Different approval paths for different project tiers: If an organization applies different approval requirements for A-level vs. B-level projects (e.g., A-level projects require stricter multi-level approval due to higher budgets), Process Templates can easily support distinct approval flows.

Different requirement form fields by product type: When managing requirements for different product categories, the required form fields often differ. For example, consumer products may require a UX Rating, while industrial products may emphasize Technical Specification Notes.

Notes

• In a process template, you can configure workflows for different objects, and you can Design, Enable, or Disable them.
• Only after a process (e.g., a Plan process) is set to Custom in the template can you enter Design to modify its workflow configuration (fields, actions, tabs, etc.). Changes made to a custom workflow do not affect common workflows or other templates; they apply only to the current template.
• Enable / Disable actions for each process within a template also apply only to the current template.
• Built-in processes within a template do not support disabling.
• Only processes that belong to Product / Project / Execution will be included in templates, and they must be enabled within the template to take effect.

1. Product Process Templates

1.1 Included Processes

A product process template includes workflows for product-related objects, including: Product, Business Requirement, User Requirement, Development Requirement, Release, Plan, Ticket, Feedback, Test Task, Test Case, Bug, and workflows that belong to Product.

1.2 Built-in Template

Product process templates include one built-in template: Default Template, which contains all product-related processes.

• Built-in templates can only be Enabled or Disabled and cannot be Designed independently.

图1

2. Project Process Templates

2.1 Included Processes

Project process templates contain workflows for project-related objects:

• Product-based Project includes: Project, Version, Execution, Task, and workflows that belong to Project / Execution.
• Project-based Project includes: Business Requirement, User Requirement, Development Requirement, Release, Plan, Ticket, Feedback, Test Task, Test Case, Bug, Version, Execution, Project, Task, and workflows that belong to Project / Execution.
• No-Iteration Project includes: Project, Version, Task, and workflows that belong to Project.
• Project-based No-Iteration Project includes: Business Requirement, User Requirement, Development Requirement, Release, Ticket, Feedback, Test Task, Test Case, Bug, Version, Project, Task, and workflows that belong to Project.

2.2 Built-in Templates

Project process templates include four built-in templates:

• Agile – Product-based Default Process
• Agile – Project-based Default Process
• Waterfall – Product-based Default Process
• Waterfall – Project-based Default Process

Notes:

• When creating a project, select an appropriate template based on the project type and model.
• Agile and Hybrid Agile projects can use Agile templates. Waterfall and Hybrid Waterfall projects can use Waterfall templates.
• Built-in templates can only be Enabled or Disabled and cannot be Designed independently.

图2

3. Maintain Process Templates

3.1 Create a Process Template

Click Add Process Template and fill in the required information in the dialog.

• For project process templates, you must additionally define the Applicable Project Model and Applicable Project Type. These settings cannot be edited after creation.
• Agile and Hybrid Agile can select Agile project templates. Waterfall and Hybrid Waterfall can select Waterfall project templates.

图3

Click Design to enter the template’s process list. Based on the rules above, the template will automatically include the corresponding object processes, and the workflows remain consistent with the configuration of the original process objects.

图4

When a new template is initialized, the included processes are Common by default. These common processes can be Enabled / Disabled. Built-in processes do not support disabling.

图5

Click Custom to switch a workflow in the template from Common to Custom. Only after it is set to Custom can you click Design to configure the workflow, including Main Table, Sub-table, Action Design, Tab Design, and other workflow settings. 【在此插入7.17.3 内置工作流的链接】

• Changes to a custom workflow take effect only within the current template and do not affect the original process object or other templates.
• After workflow configuration changes, Products or Projects using this template will be updated accordingly in the UI.
• Set to Custom is irreversible.

图6

Click Enable / Disable for a process to enable or disable that process within the template.

• After disabling, the related feature will no longer be shown in Products or Projects that apply this template.

图7

3.2 Publish / Disable a Process Template

Click Publish / Disable to publish or disable the template. Only published templates can be selected when creating Products or Projects.

• When copying a project, if the selected template has been disabled or deleted, the system will switch to the default template.

图8

3.3 Edit a Process Template

Click Edit to modify the template’s basic information.

图9

3.4 Delete a Process Template

Click Delete to remove a process template. Deleting a template does not affect workflows that are already in use.

图10