User Guide
Scoring Template
Scoring Templates define the metrics and formula used to calculate a composite priority score for each Jira issue in the Backlog Table.
Built-in Templates
ICE Score
Formula: Impact × Confidence × Ease
| Metric | Scale | Meaning |
|---|---|---|
| Impact | 1–10 | How much value does this deliver? |
| Confidence | 1–10 | How confident are we in the estimate? |
| Ease | 1–10 | How easy is it to implement? |
Best for: Feature requests and bug fixes where effort vs. value trade-offs are primary.
RICE Score
Formula: (Reach × Impact × Confidence) / Effort
| Metric | Scale | Meaning |
|---|---|---|
| Reach | Number | How many users affected per quarter? |
| Impact | 1–3 | Massive (3) → Minimal (0.25) |
| Confidence | % | Estimate reliability (100% = certain) |
| Effort | Person-months | Work required |
Best for: Product features where audience reach is a key input.
WSJF - Weighted Shortest Job First
Formula: (Business Value + Time Criticality + Risk Reduction) / Job Size
| Metric | Scale | Meaning |
|---|---|---|
| Business Value | 1–21 (Fibonacci) | Revenue or strategic value |
| Time Criticality | 1–21 | How much value is lost by delay? |
| Risk Reduction | 1–21 | Risk or opportunity enabled |
| Job Size | 1–21 | Relative effort estimate |
Best for: SAFe environments and Agile Release Train (ART) prioritisation.
Value vs. Effort
Formula: Value / Effort
| Metric | Scale | Meaning |
|---|---|---|
| Value | 1–10 | Business or user value |
| Effort | 1–10 | Implementation complexity |
Best for: Simple two-dimension ranking when speed matters over precision.
Creating a Custom Template
- In the Backlog Table, click the Template selector dropdown → Manage Templates
- Click Create New Template
- Enter:
- Template Name
- Description (optional but recommended - explain how scorers should interpret metrics)
- Add Metrics:
- Metric Name (e.g., "Customer Impact")
- Input Type: Number, Dropdown, Star (1–5), Effort Scale (XS/S/M/L/XL)
- Range (min/max for number inputs)
- Enter Formula - reference metric names using their exact labels (e.g.,
Impact * Confidence / Effort) - Click Save
Switching Templates
- Template changes apply to all issues in the current view
- Existing metric values for the old template are preserved but not shown
- Switching back restores previous values
Tips
- Document your metric definitions in the template description - ambiguous metrics lead to inconsistent scoring across team members
- Use one template consistently within a planning cycle - changing mid-sprint makes scores incomparable
- Save custom templates for your team's specific domain (e.g., a support-ticket template with Customer Impact × Frequency × Fix Complexity)