Field Defaults for Jira
Values that new work items get when their creator leaves a field empty, applied a few seconds after creation, whichever way the work item was created.
Getting started
- Install Field Defaults for Jira from the Atlassian Marketplace.
- Open Project settings → Apps → Field Defaults in a project you administer. Pick a work item type, add a default for each field you want filled, and save. Only fields on that type's create screen are offered, because Jira refuses writes to any other field.
- Create a work item any way you like: the create dialog, inline on the backlog or board, mobile, email, Automation or the API. Within a few seconds the app fills the fields that were left empty. Fields the creator set are never changed.
- Apply by hand from a work item's "…" menu with Apply field defaults, or fill a whole project's open work items from the settings page with Apply to open work items missing values.
Field types and values
| Field type | Default you can set |
|---|---|
| Text, URL | Text with variables: {{summary}}, {{key}}, {{project}}, {{type}}, {{reporter}}, {{today}}, {{today+7}}, {{name|fallback}} |
| Description, paragraph fields | A plain-text template with the same variables; blank line = paragraph, "- " = list, "# " = heading |
| Number | A number |
| Single choice, radio buttons, version | One of the field's options |
| Multiple choice, checkboxes, fix versions | Any of the field's options |
| Labels | One or more labels |
| Components | One or more of the project's components |
| Priority | A priority. Note that Jira usually sets its own default priority on create, so this only applies when the project's scheme has none |
| Assignee, people fields | The reporter, the lead of the work item's first component, the project lead, or a named person |
| Due date, date fields | A number of days after creation (negative for before) |
Not supported: people fields holding several people, sprints, time tracking, cascading selects, and the identity fields Jira owns (summary, type, project, reporter, parent).
How applying works
When a work item is created, Jira tells the app. The app reads the work item as the app, fills only the mapped fields that are empty at that moment, and writes them in one update without sending notifications. Each work item is handled once, so a repeated event never applies twice. What was set is recorded on the work item as an entity property named aldorock-field-defaults (the fields, the time and whether it was the automatic apply, the menu action or a bulk run). The automatic apply can be switched off per project; the menu action and bulk apply then still work and run as you, under your permissions.
Preview
The settings page shows what the defaults would set, either on an empty work item or on one you name by key, including which fields would be kept because they already have a value. Nothing is written by a preview.
Permissions
Jira admins and project admins change a project's defaults and run bulk applies. Anyone who can edit a work item can use Apply field defaults on it. The automatic apply runs as the app and so works for every creator, including Automation and integrations.
Limits and notes
- 30 defaults per work item type; text up to 2,000 characters, templates up to 20,000.
- A default whose field is later removed from the create screen is flagged on the settings page; Jira would reject the write until the field is back or the default is removed.
- If a write fails, the error is shown on the settings page until the next successful save.
- Team-managed and company-managed projects both work; the fields offered come from the type's create screen in that project.
Changelog
- 1.0 (November 2026): first release.
