Task Templates in GitScrum | Setup Guide
Create, manage, and use task templates in GitScrum to standardize work. Templates include descriptions, checklists, labels, and default assignees.
7 min read
Task templates in GitScrum transform how you handle recurring work. Instead of writing the same descriptions, adding the same labels, and creating the same checklists repeatedly, templates let you capture best practices once and apply them instantly.
Template Features
| Feature | Description |
|---|---|
| Pre-filled description | Standard content for task type |
| Default labels | Automatically applied labels |
| Checklists | Step-by-step items to complete |
| Custom fields | Pre-set field values |
| Placeholders | Dynamic fields to fill in |
Creating Templates
Step-by-Step Guide
CREATING A TASK TEMPLATE
════════════════════════
STEP 1: Access Template Settings
─────────────────────────────────────
Project → Settings → Task Templates
Click "Create New Template"
STEP 2: Basic Information
─────────────────────────────────────
┌─────────────────────────────────────────────────────────┐
│ Template Name: [Bug Report ] │
│ Description: [Standard bug report format ] │
│ Icon: [🐛 ▼] │
│ Category: [Development ▼] │
└─────────────────────────────────────────────────────────┘
STEP 3: Default Values
─────────────────────────────────────
┌─────────────────────────────────────────────────────────┐
│ DEFAULTS: │
│ ├── Labels: [bug] [needs-triage] │
│ ├── Assignee: [Unassigned ▼] │
│ ├── Priority: [Medium ▼] │
│ ├── Effort: [Auto-estimate ▼] │
│ └── Sprint: [Backlog ▼] │
└─────────────────────────────────────────────────────────┘
STEP 4: Description Template
─────────────────────────────────────
[Markdown editor with template content]
## Environment
- Browser/OS: {{browser}}
- Version: {{version}}
## Steps to Reproduce
1. {{step1}}
2. {{step2}}
## Expected vs Actual
Expected: {{expected}}
Actual: {{actual}}
STEP 5: Checklist
─────────────────────────────────────
☑ Default Checklist Items:
├── ☐ Bug reproduced
├── ☐ Priority assessed
├── ☐ Fix implemented
├── ☐ Tests added
└── ☐ Verified in staging
STEP 6: Save Template
─────────────────────────────────────
[Save Template]
Template Editor
TEMPLATE DESCRIPTION EDITOR
═══════════════════════════
FEATURES:
├── Markdown support
├── Placeholders: {{field_name}}
├── Conditional sections
├── Code blocks
└── Tables
PLACEHOLDERS:
├── {{title}} - Will prompt for input
├── {{date}} - Auto-fills current date
├── {{user}} - Auto-fills creator
├── {{sprint}} - Current sprint name
└── {{custom_field}} - Any custom field
EXAMPLE:
─────────────────────────────────────
## Feature Request
**Requested by:** {{requester}}
**Date:** {{date}}
### User Story
As a {{user_type}}
I want to {{goal}}
So that {{benefit}}
### Acceptance Criteria
- [ ] {{criteria_1}}
- [ ] {{criteria_2}}
- [ ] {{criteria_3}}
### Priority
{{priority_justification}}
─────────────────────────────────────
Using Templates
Creating Task from Template
USING A TEMPLATE
════════════════
METHOD 1: New Task Button
─────────────────────────────────────
Click "+" → "From Template"
Select template from list
Fill in placeholders
Create
METHOD 2: Quick Create
─────────────────────────────────────
Press "T" (keyboard shortcut)
Type template name
Press Enter
Fill in details
METHOD 3: Context Menu
─────────────────────────────────────
Right-click in board column
"New from Template"
Select template
METHOD 4: Command Palette
─────────────────────────────────────
Cmd/Ctrl + K
"Create from template: Bug Report"
Enter
AFTER CREATION:
─────────────────────────────────────
Template content pre-filled
Placeholders highlighted for input
Modify as needed
Save task
Template Picker
TEMPLATE PICKER UI
══════════════════
┌─────────────────────────────────────────────────────────┐
│ Create from Template [Search]│
├─────────────────────────────────────────────────────────┤
│ │
│ RECENT │
│ ├── 🐛 Bug Report Used 12x │
│ └── ✨ Feature Request Used 8x │
│ │
│ DEVELOPMENT │
│ ├── 🐛 Bug Report │
│ ├── ✨ Feature Request │
│ ├── 🔧 Technical Debt │
│ └── 🔬 Spike/Research │
│ │
│ OPERATIONS │
│ ├── 🚀 Deployment │
│ ├── 🔥 Hotfix │
│ └── 🛠 Maintenance │
│ │
│ TEAM PROCESS │
│ ├── 📋 Sprint Planning │
│ └── 🔄 Retrospective │
│ │
└─────────────────────────────────────────────────────────┘
Template Management
Organizing Templates
TEMPLATE ORGANIZATION
═════════════════════
CATEGORIES:
├── Development
│ ├── Bug Report
│ ├── Feature Request
│ ├── Technical Debt
│ └── Spike/Research
│
├── Operations
│ ├── Deployment
│ ├── Hotfix
│ └── Maintenance
│
├── Process
│ ├── Sprint Planning
│ ├── Retrospective
│ └── Demo Prep
│
└── Client
├── Client Request
├── Approval
└── Deliverable
PERMISSIONS:
├── View: All project members
├── Create: Project admins, leads
├── Edit: Template owner, admins
└── Delete: Admins only
Template Analytics
TEMPLATE USAGE ANALYTICS
════════════════════════
┌─────────────────────────────────────────────────────────┐
│ Template Usage (Last 30 days) │
├─────────────────────────────────────────────────────────┤
│ │
│ Template │ Uses │ Users │ Avg Time Saved │
│ ─────────────────────┼──────┼───────┼──────────────── │
│ Bug Report │ 42 │ 8 │ 5 min │
│ Feature Request │ 28 │ 6 │ 8 min │
│ Deployment │ 12 │ 3 │ 10 min │
│ Retrospective │ 4 │ 1 │ 15 min │
│ Hotfix │ 3 │ 2 │ 5 min │
│ │
│ TOTAL TIME SAVED: ~8 hours │
│ │
│ UNUSED TEMPLATES (Consider archiving): │
│ ├── Old Bug Template (0 uses, 60 days) │
│ └── Legacy Feature (0 uses, 45 days) │
│ │
└─────────────────────────────────────────────────────────┘
Advanced Features
Conditional Sections
CONDITIONAL TEMPLATE SECTIONS
═════════════════════════════
CONFIGURATION:
─────────────────────────────────────
When creating from template, ask:
☐ Has database migration?
☐ Has feature flag?
☐ Requires security review?
TEMPLATE CONTENT:
─────────────────────────────────────
## Standard Deployment Steps
1. Create release tag
2. Deploy to staging
3. Verify staging
4. Deploy to production
{{if has_migration}}
## Database Migration
- [ ] Backup database
- [ ] Test migration on staging
- [ ] Run migration in production
- [ ] Verify data integrity
{{/if}}
{{if has_feature_flag}}
## Feature Flag
- [ ] Flag created and configured
- [ ] Rollout percentage set
- [ ] Kill switch tested
{{/if}}
{{if security_review}}
## Security Review
- [ ] Security checklist complete
- [ ] Pen test scheduled (if major)
- [ ] Approval from security team
{{/if}}
Template Inheritance
TEMPLATE HIERARCHY
══════════════════
ORGANIZATION TEMPLATE (Base):
─────────────────────────────────────
"Company Bug Report"
├── Standard description sections
├── Company-wide labels
└── Base checklist
PROJECT TEMPLATE (Extends):
─────────────────────────────────────
"Mobile App Bug Report" extends "Company Bug Report"
├── + Device-specific fields
├── + App version field
└── + Platform-specific checklist items
USAGE:
├── Company template used as default
├── Projects can customize
├── Changes to base propagate (optional)
└── Project overrides preserved
Best Practices
For GitScrum Templates
Anti-Patterns
TEMPLATE MISTAKES:
✗ Too many templates (overwhelming)
✗ Too generic (not useful)
✗ Never updated (outdated)
✗ No placeholders (copy-paste needed)
✗ Missing key checklist items
✗ Unused templates cluttering list