How to Set a Default Assignee in Jira Cloud (per Project, Component or Issue Type)

Short answer: A Jira Cloud project's default assignee can only be the project lead or Unassigned. For anything more specific you can use component default assignees, an Automation rule that assigns after creation, or an app that pre-fills the Assignee in the Create dialog per project and issue type.

1. Project default assignee (native)

Company-managed: Project settings > Details > Default assignee, then choose Project lead or Unassigned. If the option is greyed out, check Settings > System > General configuration > Allow unassigned work items. When that is OFF, every issue must have an assignee and new issues go to the project lead. In team-managed projects only a Jira admin can change it.

2. Component lead as default assignee (company-managed)

Give each component a lead and set its Default assignee to "Component lead". When someone leaves Assignee on Automatic and picks that component, Jira assigns the component lead. With several components, Jira applies a precedence order (component lead first, then alphabetical by component name). The catch: it only works if people pick a component, and it does nothing for issue types.

3. Jira Automation (after creation)

Trigger Work item created, condition Work type equals Bug (and Assignee is empty), action Assign work item to a specific user, or use the "balanced workload" or "round-robin" options. Caveats: the assignment happens after the issue exists, so the creator doesn't see it in the dialog; creation notifications go out first; and runs count toward your Automation limit.

4. Pre-fill Assignee in the Create dialog with an app

If you want "Bugs in project WEB default to the QA lead, Tasks to the team lead", an app built on Jira's UI modifications can pre-fill Assignee per project and issue type, so the person creating the issue sees it and can change it.

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

Which should you use?

Need	Best option
Everything goes to one owner	Project lead as default
Owner depends on area of the product	Component leads
Owner depends on issue type, OK after creation	Automation
Owner depends on issue type, visible before Create	A defaults app

FAQ

Can I set the default assignee to a specific user who isn't the project lead? Not at project level. Use a component lead, an Automation rule, or an app that pre-fills Assignee.

Why can't I change the default assignee? If "Allow unassigned work items" is OFF in General configuration, the default is forced to the project lead. In team-managed projects only a Jira admin can change it.

Can the default assignee differ by issue type? Not natively. Automation can assign after creation, or an app can pre-fill Assignee per issue type in the Create dialog.

Will a default assignee override someone the reporter picked? Native defaults only apply when Assignee is left on Automatic. Add an "Assignee is empty" condition to Automation rules so they don't overwrite a choice.

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