Atlassian Templates

Creates and maintains Jira and Confluence templates, blueprints, and reusable content structures so teams stop rebuilding the same document or issue layout by hand.

Business & Ops / Project Managementbusiness-opsproject-management
by AgentVoltv1.0.0Published 1y ago1 install
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

PromptCreate a bug triage template for our Jira backlog
Beforegeneric AI agent
I can help you build a bug triage template for Jira. You'd want to include fields for severity, priority, and maybe some descriptors of what the bug is. You could also add fields for the affected component or team. To make this really useful for your workflow, I'd want to understand how your team currently triages bugs. What information matters most to your team—is it severity, impact, affected users? Do you want to route bugs to specific teams based on component? Are there approval steps or SLAs around triage? Once I know more about your process, I can design a template that fits your needs.
Afterwith Atlassian Templates
BUG TRIAGE TEMPLATE: Jira Custom Workflow

CUSTOM FIELDS
  1. Severity (Dropdown) - Controls SLA and escalation path
     Critical (60-min response), High (4-hour), Medium (24-hour), Low (5-day)
     Affects escalation automation and alert rules
     
  2. Business Impact (Select List) - Determines priority
     Revenue impact: None, 1-10 accounts, 10-50 accounts, 50+ accounts
     Used in priority calculation algorithm
     
  3. Root Cause Category (Dropdown) - For pattern analysis
     Infrastructure, Data model, Third-party API, Configuration, Feature defect
     Route to Platform team, Database team, Integrations team, Config team, or Product team
     
  4. Affected Component (Select List) - Links to product architecture
     API, Frontend, Database, Mobile App, Admin Panel, Integrations
     
  5. Estimated Impact Radius (Radio) - Scope understanding
     Single account, Region, All customers, Specific user segment

AUTOMATION RULES
  Rule 1: Auto-escalate Critical severity bugs
    Trigger: Issue type = Bug AND Severity = Critical
    Action: Assign to Platform Escalation Queue, Post to Slack #critical-bugs, Set SLA to 60 minutes
    
  Rule 2: Reject incomplete bug reports
    Trigger: Issue missing Root Cause Category, Business Impact, or Reproduction Steps
    Action: Move to "Awaiting Details" status, Comment: "Please complete triage fields", Notify Reporter
    
  Rule 3: Auto-route by component
    Trigger: Issue Affected Component = API
    Action: Assign to API team, Set sprint to API team's current sprint (if available)

TRIAGE WORKFLOW (5-state)
  1. New Bug → Triage (Team fills: Severity, Business Impact, Component, Reproduction Steps)
  2. Triage → Classified (Engineering lead validates field quality)
  3. Classified → Scheduled or Rejected (If incomplete, moves to Awaiting Details, loops back)
  4. Scheduled → In Progress (Dev picks up, linked to story)
  5. In Progress → Done (Fix verified, linked to release)

TRIAGE CHECKLIST (On-screen guide)
  Required on New:
    □ Reproducible step-by-step? (If no, ask reporter for clarity)
    □ Severity: Is this blocking anyone's workflow? (Yes = High minimum)
    □ Business Impact: How many customers affected? (Needed for priority)
    □ Component: Which system is broken?
    □ Environment: Production, Staging, Dev?
    □ Screenshot or video: If visual issue, must have proof
    
  Optional but helpful:
    □ Affected versions (if applies)
    □ Related bugs (link to similar issues)
    □ Workaround (if exists)

SCORING ALGORITHM (Auto-calculates Priority)
  Priority Score = (Severity weight × 0.5) + (Business Impact weight × 0.3) + (Frequency weight × 0.2)
  Score 9-10 = P0 (Fix immediately)
  Score 7-8 = P1 (Fix this sprint)
  Score 4-6 = P2 (Fix next sprint)
  Score 1-3 = P3 (Backlog)

REPORTING & INSIGHTS
  Dashboard view: Bugs by Component over time (identify patterns)
  SLA compliance: What % of Critical bugs were triaged within 60 min
  Root cause trends: Are more bugs in API or Database this month
  Triage quality: What % of bugs have all required fields filled

About this skill


name: atlassian-templates description: Use when Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content s...

Atlassian Templates

Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use when building org-wide templates, custom blueprints, page layouts, and automated content generation.

What you get

  • Public GitHub repo (alirezarezvani/claude-skills)
  • the atlassian-templates skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.

Customize your output

  • Fork the repo and adapt the skill's instructions and references to your workflow.

Example output

Activates automatically when your request matches Atlassian Templates; chains with the other skills, agents, and commands in the collection.

Best for

Creators, builders, and teams using Claude Code.

SKILL.md preview

SKILL.md
---
name: atlassian-templates
description: Use this skill when creating, modifying, or managing Jira and Confluence templates, blueprints, custom layouts, or standardized content structures.
version: 1.0.0
category: Business & Ops / Project Management
author: AgentVolt
license: proprietary
tags:
  - business-ops
  - project-management
---

# Atlassian Templates

Creates and maintains Jira and Confluence templates, blueprints, and reusable content structures so teams stop rebuilding the same document or issue layout by hand.

## When to use

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More business & ops skills

View all Business & Ops skills →