Smart Defaults for Jira

1. Install the app from the Atlassian Marketplace.
2. Go to Settings > Apps > Default values (Jira administrators only).
3. Select Create rule, choose projects and work types, set at least one value, and select Save.
4. Create a work item. A few seconds later, the empty fields are filled in.

A rule has:

• Name – for your own overview, up to 100 characters.
• Projects – leave empty for all projects. Service projects only get defaults when they are selected here.
• Work types – leave empty for all work types.
• Values – at least one of:
  • Priority – the list shows the priorities allowed in the selected projects.
  • Labels– up to 10, separated by spaces or commas. Labels can't contain spaces.
  • Components – only when the rule has exactly one project, because components belong to a project.
  • Due date (days after creation) – 0 to 365. 0 means the day the work item is created.

Please don't put personal or confidential information in rule names or labels.

Only one rule is applied to each work item: the most specific one.

1. A rule for the project and the work type
2. A rule for the project
3. A rule for the work type
4. A rule for all projects

If two rules are equally specific, the one changed most recently wins.

• Labels, components and due date are set only when the field is empty.
• Priorityis replaced only while the work item still has the project's default priority. If the reporter picked another priority, it is kept. If the reporter deliberately picks the default priority, Smart Defaults can't tell the difference and applies the rule's priority.
• If a field isn't on the work type's edit screen, it is skipped and the other fields are still set.
• If someone changes one of these fields in the seconds before Smart Defaults writes, Smart Defaults leaves the work item alone.

Defaults are applied after the work item is created, so it doesn't matter where it was created: the create dialog, the backlog, a board, a subtask, the REST API or Jira Automation. Values are not shown inside the create dialog; they appear once the work item exists, usually within a few seconds.

Clones are left alone: they already have the values of the original work item.

Team-managed projects: labels and due date work out of the box. Priority and components are set only if those fields have been added to the work type.

Service projects (Jira Service Management): only rules that name the project are used. Rules for all projects are not applied there.

• The due date is counted in calendar days, using the UTC date.
• Smart Defaults never changes the description or other fields. It works side by side with Auto Issue & Description Templates for Jira.
• Rules are stored in Atlassian's Forge hosted storage. Uninstalling the app deletes the rules. Values already set on work items stay, as normal Jira field values.

Smart Defaults uses 3 scopes: read work, write work and app storage. It has no admin scopes, sends no data outside Atlassian and stores no personal data. See our privacy policy: https://www.helkrypt.no/privacy/apps.

Email support@helkrypt.no. Please include your Jira site URL and the key of a work item that didn't get the defaults you expected. Don't send work item content.