Find the fix for your
Jira, JSM, or Confluence issue.

Welcome to Patcher for Jira Service Management What Patcher for Jira Service Management is, and how to use these docs. Customers can’t add request participants from the portal Let customers add colleagues to their own request, straight from the portal. Approvers get no reminder for pending approvals Nudge approvers until they act, and escalate to a backup when they don't. Agents can’t raise a request on behalf of a customer Log phone, chat and walk-up requests with the right customer as the reporter. Portal fields can’t be shown as read-only to customers Show customers context like SLA or assigned agent without letting them edit it. SLA timers don’t pause while waiting for the customer Stop the SLA clock while the ball is in the customer's court. Request types can’t be grouped or reordered in the portal Group and order request types the way customers actually think. Ongoing major incidents aren’t surfaced on the portal Tell customers about an active outage before they raise a duplicate ticket. SLA targets can’t differ by priority within one queue Give Critical a tighter target than Low without extra queues. Approval emails don’t include the request details Put cost, access level and justification right in the approval email. No follow-up on unanswered satisfaction (CSAT) surveys Remind customers who missed the survey, and lift your response rate. Queues can’t be shared or reordered per agent Let agents pin, reorder and share the queues that matter to them. Customer notifications can’t be tailored per request type Make a password reset and a major change read differently to the customer. Agents can’t bulk-reply or bulk-transition a queue Clear a wave of identical tickets in one pass, with an auditable response. Knowledge base articles aren’t suggested on the portal form Deflect easy questions by surfacing the right article as the customer types. Linked assets aren’t shown to the customer on their request Let customers confirm the exact device or service their request is about.

Welcome to Patcher for Jira What Patcher for Jira is, and how to use these docs. Sub-task estimates not rolling up to the parent issue Make parent totals and reports reflect the work on their sub-tasks. Bulk edit floods every watcher’s inbox with notifications Turn a thousand bulk-edit emails into one digest per person. Epic link is lost when moving issues between projects Keep stories attached to their epic across a project move. Closed sprints can’t be reopened in Jira Safely reopen a sprint closed by mistake, with its history intact. You can’t make a field required only on a specific transition Require a field at Done without forcing it on every create screen. @mentions in the description don’t always send a notification Make sure a mention in the description actually reaches the person. Custom notification emails Patcher for Jira · write your own notification emails per project: your subject, your text, any field, your design.

Welcome to Patcher for Confluence What Patcher for Confluence is, and how to use these docs. No bulk operations for pages in a space Move, archive, label and update many pages in a single pass. Page and space permissions are too coarse Give the right people the right access without over- or under-sharing. Watchers get an email for every edit, not a digest Collapse a storm of edit emails into one concise summary. No self-serve way to restore a deleted page Let authors bring back a page they deleted, without a ticket. Page analytics don’t add up See real views and trends so you know what to keep and what to prune. Macros break in the new editor Keep macros and layout intact when pages move to the new editor.