Feature Overview

Project Templates help teams create new projects faster while keeping structure, workflow, and setup consistent. By reusing predefined template content such as phases or sprints, task data, team members, project permissions, and doc structure, teams can avoid rebuilding the same project setup from scratch every time. This improves collaboration, reduces setup effort, and supports more consistent project delivery.

Use Cases

• Standardize project delivery For projects that follow the same structure and workflow, templates make it easy to reuse a proven project framework and avoid missing critical steps.
• Help new team members ramp up faster New project managers can use standard project templates to understand the team’s project structure and delivery practices more quickly.
• Capture best practices High-performing project setups can be saved as templates and reused by other team members, making it easier to spread successful practices across the organization.
• Reuse recurring project structures Templates are also useful for recurring work such as quarterly planning, annual audits, or monthly operational routines.

1. Create a Project Template

Go to Project > Project Templates to create a template

Click Create from Existing Project to turn an existing project into a project template.

图1

The project dropdown shows only non-Kanban projects that the current user has permission to view.

After you select a project, its information is automatically loaded into the template.

The Project Template Name and Project Code must be unique and cannot duplicate any existing project or project template.

Click Save to open the page for completing sprint/phase information. Then click Complete Copy to finish creating the project template.

图2

图3

2. Manage a Project Template

Click the template name to open the project template and manage its contents.

The following parts of a project template can be maintained:

• Executions
• Tasks
• Docs
• Process
• Quality Assurance
• Team Members
• Permission Groups

The entry points and operations are generally the same as in a regular project.

For Kanban-type iterations, task breakdown is supported only in list view.

图4

If you do not want other users to see the project template, you can configure its use and edit permissions.

If the template is set to Private, only the creator and users on the whitelist can use or edit the project template.

图5

图6

3. Disable or Delete a Project Template

图7

If a project template is not fully configured yet, or needs to be updated later, you can click Disable to change it to the disabled state. Disabled templates do not appear when creating a new project.

图8

If a project template is no longer needed, you can click Delete to remove it.

Deleted project templates do not go to Trash and cannot be recovered, so delete them with care.

4. Use a Project Template

Click Create Project to open the creation dialog.

The dialog shows all active project templates that the current user has permission to use.

After you select a template, its information is filled in automatically. Complete the remaining required fields and create the project.

After the project is created, open it to view the data that was carried over from the template.

图9

图10

5. Data Supported by Project Templates

Project templates can include the following types of data:

• Basic Information: project name, project code, owner, access control, permission control, task time constraints, linked requirement settings, project type, project workflow, whether sprints are enabled, phase type, approval settings, and workflow custom fields
• Execution Information: execution name, management method, execution type, access control, execution code, product owner, execution owner, test owner, release owner, and workflow custom fields
• Task Information: module, related execution, task template, task links, task type, task module, task name, priority, estimated story points, task description, keywords, CC recipients, and workflow custom fields
• Doc Information: doc structure
• Process Information: process tailoring
• Quality Assurance Information: related process, related execution, inspection target
• Project Permission Groups: permission group names and assigned permissions
• Team Members: project team members and execution team members