Jira Cloud guides

How to Set Default Labels and Components on New Jira Cloud Issues

Short answer: Jira Cloud has no built-in default value for Labels or Components; they are system fields, covered by the long-running request JRACLOUD-4812 (about 2,800 votes). You can add them after creation with Automation, or pre-fill them in the Create dialog with an app.

1. Automation: add labels or components on create

  1. Project settings > Automation > Create rule.
  2. Trigger: Work item created.
  3. Condition: e.g. Work type equals Bug.
  4. Action: Edit work item > Labels > Add "needs-triage" (use "add" rather than "set" so you don't wipe labels the user entered). Do the same for Components.

Caveats: values appear a few seconds after creation; boards, filters and notifications triggered on creation may miss them; each run counts toward your Automation limit; and you maintain one rule per variation.

2. Use a "default" label in your process instead

If you need defaults mainly for triage, filtering on labels is EMPTY or component is EMPTY can be simpler than forcing a value: a saved filter shows everything still waiting for a label.

3. Components and default assignees

Components do have one built-in behaviour, a default assignee per component, but there is no "default component" itself. See setting a default assignee.

4. Pre-fill Labels and Components in the Create dialog

An app using Jira's UI modifications can pre-fill Labels and Components when the Create dialog opens, per project and issue type, so reporters see them, keep them or remove them before clicking Create.

Default Field Values for Jira (by Loomwise) sets defaults per project and issue type for Priority, Assignee, Labels, Components, Description templates and text, number, date and single-select custom fields. The Create dialog opens with the values already filled in, and issues created from the board or backlog get their empty fields filled right after creation. Works in company-managed and team-managed projects, runs on Atlassian Forge, sends no data outside Atlassian. Free for up to 10 users, then $0.35 per user per month, billed through Atlassian. The Marketplace listing is in Atlassian's review now.

See how Default Field Values works   Read the docs · Email us for early access

FAQ

Can Jira Cloud set a default label? Not natively. Use an Automation rule that adds the label on creation, or an app that pre-fills Labels in the Create dialog.

Can I set a default component in Jira? No. Components can have a default assignee, but there's no default component. Use Automation or an app.

Will Automation remove labels the user typed? Only if you use "set". Use the "add" option for Labels and Components to keep the user's values.

Does this work in team-managed projects? Automation works in both. Loomwise Default Field Values supports company-managed and team-managed projects.

Related guides

Disclosure: Loomwise makes the apps mentioned in the cards above and wrote this guide. Not affiliated with Atlassian. Vote counts are from jira.atlassian.com as of October 2026. Last checked October 2026; Jira menus and features change, so verify in your site. Contact: hello@loomwise.app