Default Values for Jira
Try or install on the Atlassian Marketplace.
Set default field values per project and issue type. They fill the Create dialog as it opens, follow the issue type when it changes, and never overwrite what the person creating the issue typed or picked. Jira Cloud has no built-in way to do this (JRACLOUD-4812).
Getting started
- Install the app from the Atlassian Marketplace.
- Go to Jira Settings → Apps → Default Values (you need Jira admin rights).
- Click Add rule, choose projects and an issue type, set the default values, and save.
- Press Create (or
c) in one of those projects. The defaults are filled in.
Creating rules
- Projects: one or more projects the rule covers.
- Issue type: a single issue type, or All issue types.
- Fields: Summary, Description, Priority, Labels, Components, Fix versions, Assignee, Reporter, Due date, Parent and supported custom fields. Components, Fix versions and Parent need a rule with a single project.
- Preview: before you save, the editor shows which fields each project's Create screen accepts and warns about fields that are missing or can't be set.
- New-project defaults: optionally set a template that is added to every new project.
- Up to 3,000 rules per site (a Jira limit), each covering up to 1,000 project and issue type pairs.
Which rule wins
When a project has both an All issue types rule and a rule for a specific issue type, the specific rule wins field by field. Fields it doesn't set still come from the All issue types rule.
| Rule | Summary | Labels | Priority |
|---|---|---|---|
| All issue types | – | team-a | – |
| Task | [Task] | triage | High |
| Create a Story | empty | team-a | Jira default |
| Create a Task | [Task] | triage | High |
Switching issue type and editing fields
- When the issue type changes in the Create dialog, values the app filled are replaced with the new type's defaults. A value the app filled that the new type doesn't set is cleared.
- As soon as you change a field yourself, by typing, picking or clearing it, the app leaves that field alone for the rest of the dialog.
- Nothing is saved until you click Create. Existing issues are never changed.
Limits
- Sprint and Environment can't be set by apps in the Create dialog. Reporter can't be set when it isn't on the Create screen. The editor warns about these.
- A field must be on the project's Create screen to be filled.
- When you switch to an issue type whose rules don't set Priority, the priority from the previous type stays; Jira's default isn't restored.
- Defaults apply in the Create dialog only, not to issues created through the API, imports or email.
- If another app changes the same field in the Create dialog, the last one to finish wins.
FAQ
- Does it slow down the Create dialog? No. Defaults are applied in the browser as the dialog opens, usually within a second.
- Who can edit rules? Jira admins.
- What happens on uninstall? Jira removes the app's rules and stored data.
Data
Rules are stored on your Jira site as Jira UI modifications. The app keeps one value in Atlassian Forge storage: the ID of the new-project template. Nothing leaves Atlassian, and there are no outside services or analytics. A rule contains only the default values you enter, including the account IDs of any users you choose as defaults.
Pricing
Free for up to 10 users. Above that, per user per month: 11–100 $0.35, 101–250 $0.22, 251–1,000 $0.09, 1,001–2,500 $0.06, above 2,500 $0.05. For example, $35 a month for 100 users and $135.50 for 1,000. Billed by Atlassian; see the Marketplace listing for current prices.
Support
Email support@funaticilluminations.com or see the support page.