You can’t make a field required only on a specific transition
Require a field at Done without forcing it on every create screen.
Clean data at closing time shouldn’t mean a cluttered create screen. Here is how to require a field only when it matters.
The symptom
You want a field required only when an issue moves to Done, but Jira can only make it required everywhere or nowhere.
Why Jira behaves this way
Field requiredness lives in the field configuration, which is global to the field, not attached to an individual workflow transition.
The manual workaround — and why it falls short
Admins add a validator with a scripting app or make the field globally required, which either needs extra tooling or forces the field on creation too.
How Patcher fixes it
Patcher lets you require a field on a specific transition only. It stays optional during normal work and becomes mandatory exactly when it matters.
Turn it on
- Install Patcher for Jira from the Atlassian Marketplace.
- Open Patcher › Patches from your Jira admin.
- Find Transition-only required fields in the list and switch it on.
- Scope it to the projects you choose, then save — the fix is live immediately.