Default Values Everywhere for Jira — User guide
Default field values for Jira Cloud that apply wherever work items are created: the Create dialog, backlog and board inline create, the REST API, incoming email, the customer portal and automation rules.
1. Install
Install the app from the Atlassian Marketplace. It runs entirely on Atlassian Forge ("Runs on Atlassian"): no data leaves your Atlassian site.
2. Create a rule
- Go to Jira settings → Apps → Default Values Everywhere (Jira administrators only).
- Under New rule, pick a project and a work type (or All work types).
- The fields available on that project's screens are listed. Enter a default value for each field you want; leave the others empty.
- Click Save rule. Rules apply immediately.
A rule for a specific work type takes precedence, field by field, over the project's All work types rule.
Supported fields
| Field | Default value |
|---|---|
| Description | Text template (line breaks kept) |
| Labels | Comma-separated labels (no spaces inside a label) |
| Components, Fix versions, Affects versions | One or more values |
| Assignee, Reporter | A user |
| Due date, date fields | A fixed date (YYYY-MM-DD) or a relative one: +7 = 7 days after creation |
| Custom fields | Text, paragraph, number, date, date-time, URL, single and multi select, cascading select, checkboxes, radio buttons, user and multi-user pickers |
| Priority | Prefilled in the Create dialog (see limits) |
3. How defaults are applied
| Where the work item is created | What happens |
|---|---|
| Create dialog (expanded view) | Defaults are prefilled as soon as the dialog opens. Anything the user changes is kept. |
| Backlog / board inline create, REST API, incoming email, customer portal, automation rules | Within a few seconds after creation, empty fields covered by the rule are filled. Fields that already have a value are never changed. |
Every completion is recorded in the Activity log on the app's admin page (last 100 entries, kept 30 days), and the change appears in the work item's history under the app's name.
4. Known limits
- Fields required at creation can only be covered by the Create dialog: Jira refuses to create the work item before the app can act.
- Compact Create view: defaults are not prefilled until the dialog is expanded; empty fields are completed after creation.
- Priority after creation: Jira always sets the priority from the project's priority scheme, so the app does not replace it after creation. Use your priority scheme for these channels.
- CSV "External System Import" does not send a creation event, so imported work items are not completed.
- Sprint, Story point estimate, Team, Security level, attachments and fields provided by other apps are not supported.
- Changes made after creation may trigger "updated" notifications to watchers.
5. Privacy and security
- Stored: your rules and the activity log, in Atlassian's Forge storage in your site's data residency region. No work item content is stored.
- The publisher has no access to your data. Nothing is sent to external servers.
- Only Jira administrators can view or change rules; this is checked on the server for every request.
6. FAQ
Does it overwrite values people typed? No. In the Create dialog it only replaces what the user has not touched; after creation it only fills empty fields. How fast is completion after creation? Usually 4 to 7 seconds in our tests (it can take longer during Atlassian platform incidents). What happens if a default value becomes invalid (archived version, deactivated user)? The other fields are still filled; the invalid one is skipped and shown as partial in the activity log. Does it cost Forge usage for projects without rules? No. Projects without a rule do not invoke the app.
7. Support
support@klix.nc — see the support page for response times.