FAQ

Questions,
answered.

What to know before you install Patcher.

Patcher is a set of Atlassian Marketplace apps — one for Jira Service Management, one for Jira and one for Confluence — that add the most-requested features from Atlassian’s public tracker. Every entry links to its jira.atlassian.com request, with the vote count, so you can see exactly what it adds and who asked for it. Install the app, switch a feature on for the projects or spaces you choose, and it’s live.
No. Each feature is built with the extension points Atlassian provides to all Marketplace apps: portal panels, admin pages, automation triggers and macros. Nothing in your site is modified. Switch a feature off and it is gone, with your data untouched.
Patcher for Jira Service Management, Patcher for Jira and Patcher for Confluence are all available, each with the same admin experience and the same patch list format. All three are published by Hipporello, an Atlassian Marketplace Partner.
Patcher runs entirely on Atlassian Forge, inside your own Atlassian cloud. It uses only Atlassian-hosted storage and Atlassian’s own APIs — there is no third-party server, and every feature respects your existing permissions. Your data stays in your region.
Yes. Each patch is a switch per project or space. Turn it on for one team first, roll it out when you are ready, and roll it back any time.
There’s a free Starter plan for a single project, a Team plan at $3 per user / month for every patch across every project, and a custom Enterprise option. Billing goes through the Atlassian Marketplace and you can cancel anytime.
Yes. Paste the jira.atlassian.com link on the request page. If it can be built on Forge, we scope it and tell you when it ships — and it may land on the list for everyone.
Install Patcher for Jira Service Management from the Atlassian Marketplace, open the admin page, and switch on the first feature your team has been waiting for. Setup takes minutes.

Still have a question?

We’re happy to help — reach out and we’ll get back to you.