Choose your productPatcher for JiraPatcher for JSMPatcher for Confluence

The Jira features Atlassian hasn’t shipped yet.

Sub-task roll-ups, quieter notifications, epic links that survive a move — the top-voted Jira requests from Atlassian’s public tracker, built on Forge and switched on per project.

Get it on Marketplace See the patches
Popular requests still waiting
Jira Not being considered
JRACLOUD-4812
Default values of system fields
2798votes
Foreseeable future: not planned
Secure by DesignRuns on AtlassianData never leaves your siteBuilt on Forge

The patches

Pick a request. Switch it on.

Every patch is a long-standing Jira request on jira.atlassian.com, with its ticket key and vote count.

Jira Customise the emails Jira sends JRACLOUD-14255 · 335 votes on jira.atlassian.com · Write your own notification emails per project: your subject, your text, any… ✓Patched Jira Epic link is lost when moving issues between projects JRACLOUD-12590 · 370 votes on jira.atlassian.com · Move an issue to another project and its epic link silently disappears,… ✓Patched Jira Closed sprints can’t be reopened in Jira JRACLOUD-12627 · 467 votes on jira.atlassian.com · Complete a sprint by mistake and there is no native way to… ✓Patched Jira You can’t make a field required only on a specific transition JRACLOUD-12664 · 564 votes on jira.atlassian.com · Jira can mark a field required globally, but not "required only when… ✓Patched Jira @mentions in the description don’t always send a notification JRACLOUD-12701 · 661 votes on jira.atlassian.com · Mentioning a teammate in an issue description often sends no notification, so… ✓Patched Jira Sub-task estimates not rolling up to the parent issue JRACLOUD-12516 · 2,376 votes on jira.atlassian.com · Time estimates and logged work on sub-tasks don't sum up to the… ✓Patched
See all Jira patches

What it adds

Built for Jira.

01

Make the numbers add up

Roll sub-task estimates and logged work up to the parent so sprint, velocity and workload reports finally reflect reality.

02

Calm the notifications

Collapse bulk-edit storms into a digest and make description @mentions notify reliably — without going dark.

03

Protect your structure

Keep epic links intact across project moves, reopen a closed sprint safely, and require fields only on the transition that matters.

FAQ

Questions, answered.

Sub-task estimate roll-ups, bulk-edit notification digests, epic links that survive a project move, a safe way to reopen a closed sprint, per-transition required fields and reliable description @mentions — each tied to a public Atlassian request.
No. It works within your existing schemes, workflows and permissions. Toggle a patch per project and roll it back any time; nothing is changed permanently.
Yes. Every patch is a switch per project, so you can try one where it’s needed and leave the rest untouched.
Entirely on Atlassian Forge, inside your own cloud. There’s no third-party server, your data stays in your region, and every feature respects your existing permissions.
See all FAQs

One admin experience

Three apps. One Patcher.

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.

Jira Service Management Jira Confluence

Switch on your first patch today.

Install Patcher for Jira from the Atlassian Marketplace, pick a request your team has been waiting for, and switch it on.

Get it on Marketplace Explore patches