How Patcher adds a feature without touching your service project

A good patch adds exactly one thing and changes nothing else. Here's how Patcher ships real features without disrupting how your service desk works.

The fastest way to lose a service team’s trust is to “improve” one thing and break three others. Patcher is built so that switching on a patch adds the requested behaviour — and only that behaviour.

Scoped, not sweeping

Each patch targets a single, well-understood request. It’s built with the extension points Atlassian provides to all Marketplace apps — portal panels, admin pages, automation triggers and macros — so your request types, SLAs, queues and automation keep working exactly as before.

Per project, reversible

  • Toggle per project or space. Turn a feature on where it’s needed, leave the rest untouched.
  • Switch off any time. A patch is a switch, not a migration — turn it off and your site is exactly as it was.
  • Nothing to maintain. No scripts to host, no rules to babysit.

On Forge, in your site

Because Patcher runs on Atlassian Forge, the feature lives inside your own cloud. Your data never leaves home, and your admins can see exactly what each patch is scoped to do.

Fix this bug for good.

Patcher ships the real fix — install it and switch the patch on.