Patcher brings publicly requested Jira, JSM, and Confluence features to your site. Turn on what you need, where you need it.
The patches
Every patch is a long-standing request on jira.atlassian.com, with its ticket key and vote count, so you know exactly what it adds and who asked for it.
From a Marketplace install to a live feature — without touching your workflows, schemes or permissions.
Add Patcher for Jira Service Management to your site. It’s a standard Forge app, so it runs on Atlassian infrastructure and keeps your data in your region.
Open the Patcher admin page, find the request your team has been voting for, and switch it on for the projects or spaces you choose.
The feature appears where it belongs — the portal, the issue view, the page. Switch it off any time and your site is exactly as it was.
Stays in Atlassian
Patcher uses only Atlassian-hosted storage and Atlassian’s own APIs. There’s no third-party server, and every feature respects your existing permissions.
Per project, your call
Each patch is a switch per project or space. Turn it on for one team first, roll it out when you’re ready, roll it back any time.
Request a patch
Paste the jira.atlassian.com link. If it can be built on Forge, we scope it and tell you when it ships.
Contact
Questions, a demo or a partner enquiry. Patcher is built by Hipporello, an Atlassian Marketplace Partner.
FAQ
One admin experience
Patcher for Jira Service Management, Patcher for Jira and Patcher for Confluence share the same admin page, the same switches and the same patch list format.
Install Patcher for Jira Service Management from the Atlassian Marketplace, pick a request your team has been waiting for, and switch it on.