Field Defaults & Rules for Jira
Set the right field values automatically, no scripts required.
Teams rely on fields being set correctly, but people forget and post-function scripts are hard to maintain. Field Defaults & Rules applies default values automatically when issues are created or transitioned, configured in a visual rule builder.
Create issueIllustrative preview · Example data
Every forgotten field becomes someone's cleanup job.
Jira's built-in defaults only go so far. When priority, components or due dates depend on context, teams either train everyone to remember or maintain Groovy post-functions that exactly one person understands.
Admins inherit the scripts, support teams inherit the miscategorised issues, and reporting inherits the gaps.
Best for
- Jira administrators
- Project leads
- Support and operations teams
- Engineering managers
Rules set the fields, people do the work.
Build a rule visually (trigger, conditions, the fields to set) and it applies on issue create and on workflow transitions. Standard and custom fields are supported, and every rule stays visible and editable without code.
Three steps from setup to result.
Open the rule builder
Start a rule from the admin view; no scripting environment, no deployment.
Define the trigger and conditions
Fire on issue create or a workflow transition, with conditions on issue type, labels and other fields.
Set the fields
Name the standard or custom fields the rule may set; the app writes only those fields, nothing else.
What this app helps your team do.
Visual rule builder
Create and edit rules without Groovy, scripts or consultants.
Create and transition triggers
Rules run when issues are created and when they move through workflow transitions.
Standard and custom fields
Set any supported field, with conditional logic to decide when.
Least-privilege writes
A rule writes only the fields it names; nothing else in the issue changes.
Limits and requirements, explained upfront.
- Jira Cloud only.
- Rules set default values; they do not validate or block submissions.
- Writable field types depend on what the Jira Cloud APIs expose.
What setup and ongoing management look like.
Rules are managed by Jira admins in a single rule list and can be edited or disabled at any time. Rule definitions are stored in Forge storage inside your Atlassian tenant. Removing the app deletes its stored rules; field values already written to issues remain as ordinary Jira data.
What the app can access, and why.
Check the app's runtime, permissions, storage and external connections before enabling it. These details are specific to this app.
Field Defaults & Rules runs on Atlassian Forge with zero external network egress; computation and storage stay inside your Atlassian cloud tenant.
- Runs on
- Atlassian Forge; the app runs inside Atlassian's cloud platform.
- Reads
- Issue data needed to evaluate rule conditions, through Forge APIs.
- Can change
- Only the fields a rule names, on the issues that rule applies to.
- Stores
- Rule definitions and configuration.
- Storage location
- Forge storage inside your Atlassian cloud tenant.
- External connections
- None; zero external network egress.
- Data retention
- Rules are kept until you delete them or uninstall the app, which removes the app's Forge storage.
- AI use
- None.
Pricing will appear with the marketplace listing.
This app is not yet publicly available. Current pricing and billing terms will appear here after its marketplace listing is live.
Support from the people responsible for the app.
Tell us which app you're using, where the issue occurred, what you expected and what happened instead. We aim to respond within two Australian business days.