Why this matters for ITSM teams
ITSM is a discipline of shape. Every change record has a structure - approvals, risk, implementation plan, post-implementation review. Every major incident has a structure - comms, impact, escalation, war-room, PIR. Every problem has a structure - symptom, hypothesis, investigation, RCA. Every service request has a structure - approval, fulfillment, verification, closure. ITIL prescribes the shape; the team’s quality depends on producing it consistently.
Native Jira doesn’t enforce the shape. Issue types are containers; the ITIL structure inside each ticket is rebuilt by memory and convention on every ticket. The consequence is variable change records, inconsistent major-incident handling, shallow problem investigations, and audit findings that flag the lack of standardization.
STM Issue Templates makes the ITIL shape a system feature. Standard, normal, and emergency change templates produce ITIL-shaped change records. Major-incident templates produce the right sub-task list at declaration. Problem templates carry the RCA scaffold. Service-request templates align fulfillment across teams. The audit walkthrough finds the shape it expects to find, because the platform enforces it.
Where this fits in the ITSM workflow
- Change management - templates per change category enforce the ITIL change-record shape; audits find consistency.
- Major incident - the major-incident template creates the full response sub-task list at declaration; PIR has the right data because the structure was always there.
- Problem management - the problem template carries the RCA scaffold; investigation depth stays consistent across problems.
- Request fulfillment - service-request templates per category align fulfillment across teams; leavers and starters get the same shape every time.
What “good” looks like
Good is the ITIL auditor sampling change records and finding the same shape on every one - because the template enforced it from creation, not because each requestor remembered to add the right sub-tasks. STM Issue Templates exists so ITSM teams can run ITIL-aligned operations consistently without relying on memory and convention.
What itsm teams are dealing with today
- Change tickets are missing CAB-approval and risk-assessment sub-tasks because the standard sub-task list is rebuilt by memory each time.
- Major-incident tickets lack the comms, root-cause, and post-mortem sub-tasks - so PIR (post-incident review) discovers gaps weeks later.
- Problem tickets don't carry the standard root-cause-analysis scaffold - so problem management produces inconsistent investigation depth.
- Service request tickets vary in shape from one fulfillment team to another - making cross-team reporting unreliable.
- New ITSM agents learn the team's ticket-shape conventions slowly - producing variable triage quality during onboarding.
- ITIL audits flag inconsistent change records because native Jira doesn't enforce the standard change-record shape.
How STM Issue Templates helps itsm teams
Change-record templates
Standard, normal, and emergency change templates each pre-populate the ITIL-aligned change-record fields, CAB-approval sub-task, risk-assessment sub-task, and implementation-plan scaffold.
Major-incident templates
Major-incident template creates the standard sub-task list - declare comms, capture impact, escalate, run war-room, post-mortem - so no major incident slips through without the right structure.
Problem-management scaffolding
Problem template carries the root-cause-analysis scaffold - symptom, hypothesis, investigation, root cause, corrective action - so problem records are consistently deep.
Service-request consistency
Service-request templates per category (access, hardware, software, leaver) pre-populate the fulfillment sub-tasks - so SRs are processed consistently across fulfillment teams.
Audit-defensible change records
Templates enforce the change-record fields and approval sub-tasks that ITIL and audit expect - so change records hold up to walkthrough.
Use cases
- Normal-change template. Normal-change template pre-populates change-record fields, creates CAB-approval and risk-assessment sub-tasks, and scaffolds the implementation plan. Change records arrive ready for CAB review.
- Major-incident declaration. Major-incident template creates comms, impact-capture, escalation, war-room, and post-mortem sub-tasks. Major-incident handling becomes consistent across declarations.
- Problem-management RCA. Problem-record template carries the structured RCA scaffold. Problem reviews compare investigation depth across problems because the scaffold is consistent.
- Leaver-account service request. Leaver SR template creates account-disable, access-revoke, equipment-return, and final-handover sub-tasks. Leaver process stays consistent across HR triggers.
Common questions from itsm teams
How does this help with ITIL audit?
ITIL audits typically sample change records, problem records, and major-incident records and walk through the shape - approvals, risk assessments, RCAs, post-mortems. Native Jira does not enforce that shape; auditors regularly find inconsistency. STM templates enforce the shape at creation - so the auditor's sample arrives with the standard fields and sub-tasks in place, supporting audit-defensible change-management and problem-management evidence.
Can we have different templates for standard, normal, and emergency changes?
Yes. Standard changes (pre-approved, low-risk), normal changes (CAB-approved), and emergency changes (post-implementation review) each have different shapes - different approval sub-tasks, different documentation requirements. Define a template per change category; change requestors pick the right template at creation; the change record arrives in the right ITIL shape.
Will this work alongside our ITSM workflow rules?
Yes. STM creates the ticket shape; the project's workflow rules continue to govern transitions and approvals. The two complement each other - templates produce the right ticket, the workflow governs its progression. Automation rules, SLAs, and reporting all continue to operate normally on template-created tickets.
Does this help with major-incident response?
Yes. Major incidents are the worst time to rely on memory for the standard response sub-tasks - declare comms, capture impact, escalate, run war-room, post-mortem. The major-incident template pre-creates the full sub-task list at declaration. PIR (post-incident review) consistently has the right data because the structure was in place from the start, not bolted on after the fact.
Try STM Issue Templates for your team
STM Issue Templates works for itsm teams on Jira Cloud and Data Center. Install from the Atlassian Marketplace, or read the main STM Issue Templates page for the full feature list.
Try STM Issue Templates on the Atlassian Marketplace ↗ See the full STM Issue Templates overview →
Also built for
STM Issue Templates solves a different problem for each team: