Smart Defaults – Field Rules for Jira: documentation
Smart Defaults fills in and controls fields on the Jira create form. You choose the projects and issue types, and the app sets default values, description templates and required, hidden or read-only fields. Issues created outside the form get the default values right after they are created, and sub-tasks copy values from their parent.
Open the settings
After installing, go to Jira settings → Apps → Manage apps, open Smart Defaults and select Configure. Only Jira administrators can change the rules.
Create your first rule
A new installation has no rules, so nothing changes in Jira until you create one. Choose a goal to start the guided setup:
- What do you want to do? Set default values, add a description template, make fields required, change a field based on another field, or copy values from the parent to sub-tasks.
- Where should it apply? All projects or selected projects, and all issue types or selected issue types.
- Details. For example the default priority or the template text.
- Check and create. The summary shows what the rule does. You can change everything later.
You can also start from a blank rule.
Rule settings
- Where the rule applies: projects, issue types and screens. The create form is supported. The issue view and transition screens are still in preview at Atlassian: there the app can hide fields or make them read-only, but it doesn’t set defaults, and required fields aren’t enforced on the issue view.
- Fields: a default value, and whether the field is required, hidden or read-only. A default fills an empty field when the form opens. The priority is always set, because Jira gives every issue a priority.
- Conditions: “When field is any of values, then make field required, optional, hidden or visible.” Conditions are checked every time the watched field changes. You can watch Priority, Components, Affects versions and Fix versions.
- Sub-tasks: copy priority, components, fix versions, labels, assignee and due date from the parent issue. Values go into empty fields. The priority is copied if the sub-task still has Jira’s default priority. This also works for sub-tasks created directly from the parent issue.
- Issues created outside the form: when switched on, issues created by email, import, automation or the REST API get the default values in empty fields right after they are created. The priority is set if the issue still has Jira’s default priority. Required, hidden and read-only only apply on the form.
How rules combine
Several rules can apply to the same form. For each field, the most specific rule that lists the field decides: a rule for one project and issue type beats a rule for one project, which beats a rule for one issue type in all projects, which beats a rule for everything. This lets you set defaults for all projects and add exceptions for one project.
Preview
The preview next to the rule editor shows the create form as your users will see it, including which rule set each value and which condition is active. Change the project, issue type or field values in the preview to test conditions before saving.
Supported fields
Summary, Description, Priority, Components, Labels, Assignee, Due date, Affects versions and Fix versions. Jira doesn’t let apps change the Environment field. Custom fields are not supported yet.
Good to know
- The create form shows Jira’s own values for one to four seconds before the rules are applied. This is how Jira loads apps on the create form.
- A field must be on the project’s create screen for a rule to change it.
- The create form opens from the Create button and the c keyboard shortcut. When a sub-task is created directly from the parent issue, Jira may use quick create without the form; the sub-task then gets the parent’s values right after it is created.
- The Jira Service Management customer portal is not supported.
Data and permissions
The app runs on Atlassian’s Forge platform and has no external connections. Rules are stored in Forge storage in your Jira site.
Data residency: the rules (names, projects, issue types, default values, description templates and conditions) are in scope. They are kept in Forge hosted storage, which follows your site’s data residency location. App logs (issue keys and field names) are out of scope and are kept by Atlassian’s Forge logging.
The app asks for these permissions:
- Manage Jira configuration (manage:jira-configuration): create the UI modifications that apply your rules to the form.
- Read Jira work and users (read:jira-work, read:jira-user): read projects, issue types, components, versions and the parent issue. Jira requires these permissions for apps that change the create form.
- Write Jira work (write:jira-work): fill empty fields on issues created outside the form and on new sub-tasks.
- App storage (storage:app): keep your rules.
Privacy policy: https://hdsoft.fi/en/products/atlassian/smart-defaults/privacy/
Support
Email support@hdsoft.fi. Support hours and response times: https://hdsoft.fi/en/products/atlassian/support/
