Atlassian documents personal and shared responses, rich formatting, built-in variables, and limits of 100 personal responses per agent/admin plus 250 shared responses per service project. Atlassian also documents a personal-signature pattern. Read the current native documentation before choosing an app.
Capability comparison
| Need | Native JSM canned responses | CloseReply |
|---|---|---|
| Best fit | Reusable replies inside one Jira Service Management project | A governed reply workflow shared across Jira projects |
| Library scope | Personal or shared within a service project | One administrator-managed library across service, software, and business projects |
| Variables | Documented built-in JSM variables | Built-in Jira values plus available custom Jira fields by stable field ID |
| Formatting | Rich formatting, links, and lists | Rich formatting, links, lists, code, quotes, and live preview |
| Signatures | Personal signature created from a canned response for each service project | Personal → project → global signature fallback |
| Reusable media | Use the native editor for reply content | Up to five inline images and five reusable files per template, within documented size limits |
| After-send work | Reply text remains separate from workflow changes | Optionally prepare field updates, a transition, or a follow-up request for review |
| Customer portal | Native canned responses are used by agents | An admin-approved text-only subset can appear while a customer approves or declines a pending JSM approval |
| Import | Native library | JSON/CSV import for CloseReply or Canned Responses Pro structures; no direct native-JSM import today |
Choose native JSM canned responses when
- The team works mainly inside one service project.
- Personal and project-shared replies match the ownership model.
- The documented built-in variables cover the dynamic information required.
- The reply does not need reusable attachments or a combined follow-up workflow.
Evaluate CloseReply when
- The same approved reply needs to be found across multiple Jira projects.
- Custom Jira fields should resolve into the response.
- Templates need reusable files, inline images, or layered signature fallback.
- An agent should review a reply together with field updates or a workflow transition.
- A queue-based bulk workflow or request creation from a template would remove repeated steps.
Important boundaries
CloseReply’s standard reply action works on Jira work items. Its close, approval, queue, portal, and request-creation flows depend on Jira Service Management contexts. Portal templates are available only for pending approvals and are intentionally text-only. CloseReply does not create true Jira mentions, does not claim a verified mobile experience, and does not directly import the native JSM library today.
A low-risk evaluation
Keep the current native library in place. Import a small starter set into CloseReply, choose two projects, and test the full sender review with real field configurations and permissions. Expand only if the shared workflow clearly reduces duplication or missed steps.
Build one shared Jira response library.
Start with the free template pack, or evaluate CloseReply on Atlassian Marketplace.