How to Set a Default Value for a Field on Create in Jira Cloud (2026)

Short answer: In Jira Cloud you can set a default value for custom fields (through field contexts in company-managed projects, or on the work type screen in team-managed projects) and a default priority (through priority schemes). You can't set a default for most system fields, such as Labels, Components, Assignee (beyond "project lead" or "unassigned"), or Description in company-managed projects. That request, JRACLOUD-4812 "Default values of system fields", has about 2,800 votes and has been open since 2004. For those fields you need Automation (which runs after the issue is created) or an app.

What Jira can and can't default natively

Field	Company-managed	Team-managed
Custom text, number, date, select fields	Yes, per field context	Yes, on the work type's field settings (local fields)
Priority	Per project via a priority scheme (not per issue type)	Per issue type in project settings
Description	No (KB workaround with a custom field and post functions)	Yes, per work type
Assignee	Project lead, unassigned, or component lead only	Limited
Labels, Components, Fix version	No	No
Summary	No (JRACLOUD-75592)	No

1. Custom fields: use a field context (company-managed)

Go to Settings (gear) > Work items > Fields (older sites: Issues > Custom fields).
On the field, choose More actions > Contexts and default value.
Click Edit Default Value on the context, enter the value, and save.

Limits: one context per project, so a different default per issue type in the same project means splitting contexts by issue type. Creating a new context on a field that already has values can cause data loss; Atlassian has a KB article on doing it safely.

2. Custom fields in team-managed projects

Go to Project settings > Work types (Issue types), pick the type, open the field and set its default. Watch out: for global custom fields added to a team-managed project, the default may not save (JRACLOUD-80731). Atlassian's workaround is to create a local field instead.

3. System fields: Jira Automation (after creation)

Trigger Work item created, add a condition (issue type, empty field), then Edit work item to set Labels, Components, Assignee or Description. This works for every creation path, but:

The user doesn't see the value in the Create dialog, so they can't review it.
Notifications and other "created" rules may fire before the edit.
Each run counts toward your plan's Automation limit.
You need one rule (or branch) per project and issue type combination.

4. Scripting and field-behaviour apps

ScriptRunner Behaviours and similar "field behaviour" apps can set values in the Create dialog. They're powerful, but you write and maintain scripts, and they're priced as general-purpose suites.

5. A dedicated defaults app

Single-purpose apps use Jira's official UI modifications API to pre-fill the Create dialog, so people see and can change the defaults before they click Create. Ours is below; other Marketplace options include "Default Values for 'Create Issue' screen" and several template apps.

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 option should you use?

Situation	Best option
One custom field, same default everywhere	Field context default
Default priority per project	Priority scheme
System fields, fine if set after creation	Automation
System fields, visible in the Create dialog, per issue type	A defaults app

FAQ

Can Jira Cloud set default values for system fields? Only partly. Priority (via priority schemes) and Description (team-managed only) have defaults; Labels, Components, Fix version and Summary do not. JRACLOUD-4812 tracks the request.

Why is my custom field default not showing on Create? Check that the field is on the project's create screen, that the context covers that project and issue type, and, in team-managed projects, whether it is a global field (JRACLOUD-80731).

Can I have different defaults per issue type? For custom fields, yes, with one context per issue type group. For system fields, not natively; use Automation or an app.

Does a default overwrite what the user types? Native defaults and UI-modification apps only pre-fill the form, so the user can change them. Automation edits after creation and can overwrite, so add an "is empty" condition.

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