Patcher for Jira docs
8 known issues — each with the cause, the workaround, and the Patcher fix.
1
Welcome to Patcher for Jira
What Patcher for Jira is, and how to use these docs.
Overview
2
Sub-task estimates not rolling up to the parent issue
Make parent totals and reports reflect the work on their sub-tasks.
Sub-task estimate roll-up
3
Bulk edit floods every watcher’s inbox with notifications
Turn a thousand bulk-edit emails into one digest per person.
Bulk-edit digest
4
Epic link is lost when moving issues between projects
Keep stories attached to their epic across a project move.
Preserve epic link on move
5
Closed sprints can’t be reopened in Jira
Safely reopen a sprint closed by mistake, with its history intact.
Reopen sprint
6
You can’t make a field required only on a specific transition
Require a field at Done without forcing it on every create screen.
Transition-only required fields
7
@mentions in the description don’t always send a notification
Make sure a mention in the description actually reaches the person.
Reliable description mentions
8
Custom notification emails
Patcher for Jira · write your own notification emails per project: your subject, your text, any field, your design.
Don’t see your issue?
Paste the Atlassian request link and we’ll scope it — it may land on this list for everyone.