Project Templates
Create reusable project templates for consistent project setup.
Project Templates
Project Templates let you standardize project creation. Save time and ensure consistency by creating templates for common project types.
Screenshot needed � add an annotated image showing this UI
What Are Project Templates?
Templates pre-define:
- Task structure
- Default assignees
- Cycles/sprints
- Labels and custom fields
- Settings and permissions
Creating a Template
From an Existing Project
- Open a project you want to use as template
- Go to Project Settings
- Click Save as Template
- Name the template:
- "Website Launch"
- "Product Sprint"
- "Client Onboarding"
- Choose what to include:
- Tasks
- Cycles
- Labels
- Team members
- Settings
- Click Save Template
From Scratch
- Go to Projects > Templates
- Click New Template
- Configure template structure:
Template Details:
| Field | Description |
|---|---|
| Name | Template name |
| Description | What it's for |
| Default assignee | Who gets tasks by default |
| Default priority | Task priority level |
- Add template tasks (see below)
- Save
Template Structure
Template Tasks
Define tasks that will be created:
Project: Website Redesign
├── Phase 1: Discovery
│ ├── Task 1: Stakeholder interviews
│ ├── Task 2: Competitive analysis
│ └── Task 3: Requirements doc
├── Phase 2: Design
│ ├── Task 4: Wireframes
│ ├── Task 5: Visual design
│ └── Task 6: Design review
└── Phase 3: Development
├── Task 7: Frontend build
├── Task 8: CMS integration
└── Task 9: QA testingTask Properties
For each template task, set:
| Property | Options |
|---|---|
| Title | Task name |
| Description | Details and acceptance criteria |
| Status | Default status (usually Backlog) |
| Priority | Low, Normal, High, Urgent |
| Assignee | Specific person or role |
| Labels | Categorization tags |
| Estimate | Time estimate |
| Due offset | Days from project start |
Use relative due dates like "+7 days" to set due dates based on project creation date.
Cycles in Templates
Include sprint structure:
Cycle 1: Week 1-2 (Discovery)
Cycle 2: Week 3-4 (Design)
Cycle 3: Week 5-6 (Development)When project is created, cycles are generated with appropriate dates.
Labels
Define standard labels:
designdevelopmenturgentclient-feedbackblocked
Using Templates
Creating a Project from Template
- Go to Projects > New Project
- Select From Template
- Choose your template
- Configure:
- Project name
- Start date
- Team members
- Customizations
- Click Create Project
What Gets Created
From the template:
- ✅ All tasks with properties
- ✅ Cycles with dates
- ✅ Labels
- ✅ Default settings
You can modify before finalizing:
- Edit task titles
- Reassign tasks
- Adjust dates
- Add/remove tasks
Setting a Default Template
Set a template as default for new projects:
- Go to Projects > Templates
- Find the template
- Click ... menu
- Select Set as Default
- All new projects use this template
The default template is pre-selected but can be changed during project creation.
Managing Templates
Edit Template
- Go to Projects > Templates
- Click on the template
- Make changes
- Save
Changes apply only to future projects. Existing projects are not affected.
Duplicate Template
Create a variant:
- Click ... on a template
- Select Duplicate
- Rename and modify
- Save as new template
Delete Template
- Click ... on a template
- Select Delete
- Confirm
Deleting a template doesn't affect projects created from it. Future projects just can't use the deleted template.
Template Examples
Software Development Sprint
Sprint Template
├── Planning
│ ├── Sprint planning meeting
│ └── Task breakdown
├── Development
│ ├── Feature development
│ ├── Code review
│ └── Unit testing
├── QA
│ ├── QA testing
│ └── Bug fixes
└── Release
├── Deployment
└── Sprint retrospectiveMarketing Campaign
Campaign Template
├── Strategy
│ ├── Campaign brief
│ └── Target audience research
├── Creation
│ ├── Copywriting
│ ├── Design assets
│ └── Landing page
├── Launch
│ ├── Channel setup
│ ├── Launch
│ └── Monitoring
└── Analysis
├── Performance report
└── Optimization planClient Onboarding
Onboarding Template
├── Kickoff
│ ├── Welcome call
│ ├── Account setup
│ └── Team introductions
├── Setup
│ ├── Configuration
│ ├── Data import
│ └── Integration
├── Training
│ ├── Admin training
│ ├── User training
│ └── Documentation review
└── Launch
├── Go-live
└── 30-day check-inBest Practices
Template Design
- Keep templates focused (one project type per template)
- Include all standard tasks
- Use descriptive task names
- Add clear descriptions
Maintenance
- Review templates quarterly
- Update based on process changes
- Remove outdated templates
- Get team feedback
Customization
- Balance structure with flexibility
- Allow for project-specific additions
- Don't over-template (too rigid)
- Document when to use each template