Jira Service Management’s native canned responses include documented variables for details such as reporter, assignee, work-item key, summary, status, resolution, and portal URLs. Review the current list in Atlassian’s create-a-canned-response guide before adding an app.
Use a variable only when Jira is the source of truth
Variables are most useful for values already maintained on the work item: a customer name, service tier, target date, affected system, or approval owner. Do not turn judgment into a placeholder. A root cause, remediation promise, or customer-specific explanation should still be written and reviewed by a person.
Prefer stable field IDs for custom data
Jira custom-field names can change and two fields can share a similar label. CloseReply’s picker shows the readable field name alongside its stable ID, then stores a token such as{{customfield_10042}}. That keeps a saved template connected if an administrator later renames the field.
Built-in options use readable tokens including {{issueReporter}},{{issueKey}}, {{issueSummary}}, and{{requestStatus}}. The editor inserts the exact token, and CloseReply resolves it from the current Jira work item when the response is prepared.
A safe template pattern
Hi {{reporterFirstName}},
We have reviewed {{issueKey}} for {{customfield_10042}}. Its current status is {{requestStatus}}.
Add the human explanation and confirmed next step here.
- Insert variables through the picker rather than typing IDs from memory.
- Open a representative work item where every required field has a value.
- Check the resolved preview for punctuation, blank values, and awkward sentences.
- Test a second work item with optional fields empty.
- Train agents to stop and edit any unresolved token before sending.
Design for missing values
A custom field can be empty, hidden by context, or unavailable to the current user. Write the sentence so a missing optional value does not create a misleading promise. If the field is essential, make it required in the Jira workflow or tell the sender explicitly to confirm it in the preview.
When CloseReply is the useful extension
Choose CloseReply when the team needs custom Jira fields beyond the native variable set, wants the same response across several Jira projects, or needs variables combined with files, signature fallback, and reviewed follow-up actions. For a small service-project library using only native fields, start with JSM’s built-in option.
Build one shared Jira response library.
Start with the free template pack, or evaluate CloseReply on Atlassian Marketplace.