> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/rules/pre-fill-field.md).

# Pre-fill field: automatically set a Jira field value on load

Pre-fill a Jira field when the screen loads, based on the space, work type, user, group, or another field. Conditional default values, no scripting.

Field Rules can automatically pre-fill a Jira field when a screen loads, before the user touches the form. Set the value based on the space, work type, the current user, their group or role, or another field's value, and optionally chain pre-fills so one value drives the next. It is a conditional, context-aware default value that Jira's built-in field defaults cannot provide, configured with no scripting. Unlike [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md), which reacts to user input, this rule runs once at initialization.

***

## How to set it up

1. Open the **UI Modification** for the context you want to control (space, work type, and view).
2. Add a **Pre-fill field** rule and choose the field under **Field name**.
3. Enter the **Field value** to assign when the screen loads. For Description or Paragraph fields this is a rich text editor (see [Rich text editing](#rich-text-editing)). For a user field, the value can be **Current user**, the person viewing the screen, alone or together with other users.
4. Choose whether to **Override the field value initialized when the screen loads**. Enabled (default) always sets the value; disabled only fills the field when it is empty.
5. *(Optional)* Add **preconditions** - field values and/or user identity - so the pre-fill only applies when they match.
6. Save. The value is applied when the screen loads and any preconditions pass.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-44c5457cdd8a710e6ea61df9b80a090af11129ab%2Fpre-fill-rule-description-template.png?alt=media" alt="Configuring a Pre-fill field rule that fills the Description with a bug-report template using the rich text editor"><figcaption><p>Pre-filling the Description with a bug-report template on the create screen.</p></figcaption></figure>

| Option                                                         | Description                                                                                                                                               |
| -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Field name**                                                 | The field to pre-fill.                                                                                                                                    |
| **Field value**                                                | The value to assign when the screen loads.                                                                                                                |
| **Override the field value initialized when the screen loads** | When enabled, the rule always sets the value, replacing any existing one. When disabled, the rule only applies if the field is empty. Enabled by default. |
| **Preconditions**                                              | Optional field and/or user conditions that must be true for the rule to apply.                                                                            |

***

## How it works

The rule runs when the screen initializes. If the configured preconditions pass, the field is set to the configured value. The rule does not fire again unless the screen is reloaded.

What counts as an "existing value" depends on the context:

* **Global Issue Create** - the field's configured Jira default value.
* **Issue Transition** - the field's current value on the work item.

Preconditions are evaluated against each field's current value when this rule runs, not its value before the screen loaded. This includes a value already set by an earlier **Pre-fill field** rule in the same UI Modification, which is what makes chained defaults possible: pre-fill one field, then use its value as a precondition for a later rule.

***

## Override the field value initialized when the screen loads

This setting controls whether the rule runs when the target field already has a value.

| Setting           | Behaviour                                                                              |
| ----------------- | -------------------------------------------------------------------------------------- |
| Enabled (default) | The field is always set to the configured value on load, replacing any existing value. |
| Disabled          | The rule only applies if the field is empty when the screen loads.                     |

When disabled, the rule respects values that were already present - for example, the current work item value on a transition screen, or the Jira-configured default on the create screen.

***

## Rich text editing

When the target field is **Description** or a **Paragraph** custom field, the value input changes to a rich text editor. The editor outputs content in Atlassian Document Format (ADF), which is the format those fields require.

Supported formatting:

* **Text styles** - Normal text, Heading 1 through Heading 6
* **Inline** - Bold, Italic, Underline, Strikethrough, Inline code, Subscript, Superscript, Text color
* **Blocks** - Bullet list, Ordered list (nested up to 6 levels), Blockquote, Code block, Horizontal rule
* **Tables** - insert a table, add or remove rows and columns, and resize columns
* **Links** - inline hyperlinks with `http`, `https`, or `mailto` URLs

***

## Examples

**Bug report template**\
When a Global Issue Create screen loads for Bugs, pre-fill the Description with a ready-made template - Steps to reproduce, Expected result, Actual result - using the [rich text editor](#rich-text-editing). Keep the override setting on so that if the user switches work type, the correct template is re-applied instead of Jira keeping the previous text.

**Per-work-type templates with a default fallback**\
Add several Pre-fill field rules for the Description in one UIM: a first rule with no condition that sets a generic template for every work type, then targeted rules with an Issue Type condition (for example a Bug template and a Story template). Because rules run in sequence and the last matching rule wins, each work type gets its specific template while everything else falls back to the default. Keep override on so the targeted rules replace the default and re-apply when the user changes work type. See [Execution order](https://docs.forgappify.com/field-rules/jira-administrator/execution-order.md) for how sequencing works.

**Default component by space**\
When a Global Issue Create screen loads for the "Platform" space, pre-fill the Component field with "Core". Useful when a space maps cleanly to a single team or component.

**Pre-select resolution on transition**\
When a "Close" transition screen loads, automatically set the Resolution field to "Done". Enable the override setting to ensure it is always applied regardless of the field's current value.

**Pre-fill a rich text template on transition**\
When a "Close" transition screen loads, set Resolution to "Done" and pre-fill a "Closure summary" paragraph field with a formatted template using the [rich text editor](#rich-text-editing), so the person closing the work item starts from a structured summary instead of a blank field.

<figure><img src="https://1561395444-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOfQTst0rZQxXAZF84TB5%2Fuploads%2Fgit-blob-5a4ca3a8ae35dc5d73aeb54362be1151da686b5a%2Fpre-fill-on-transition.gif?alt=media" alt="The Close transition screen opens with Resolution already set to Done and a Closure summary paragraph pre-filled with a formatted template"><figcaption><p>Pre-filling Resolution and a formatted "Closure summary" template as the Close transition screen opens.</p></figcaption></figure>

**Conditional priority default**\
When a Global Issue Create screen loads and the current user belongs to the "Support" group, set Priority to "High". Enable the override setting, as Priority always initializes with a default value on the create screen.

**Current user as the default**\
When a Global Issue Create screen loads, pre-fill a "Requested by" user picker with **Current user**, so the person creating the work item is recorded without having to pick themselves.

**Field-conditioned default assignee**\
When a Global Issue Create screen loads and the Issue Type is set to "Incident", pre-fill the Assignee with the incident lead.

***

## When to use it

Use Pre-fill field to seed a value before the user sees the form, saving repetitive selections and reducing errors:

* **Context defaults** - set a value that depends on the space, work type, user, or group, which Jira's field defaults cannot vary.
* **Transition pre-population** - set Resolution or another field automatically on a transition, where Jira has no default-value support.
* **Chained defaults** - pre-fill one field, then use its value as a condition for later rules in the same UIM.

Use [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md) instead when the value should update in response to what the user does after the form loads.

***

## Doing this without Field Rules

Jira's built-in default value configuration works at the field context level. To set different defaults per work type, you must create a separate context for each - duplicating the full option list each time. It also cannot vary the default by user, group, or another field's value, and does not apply to transition screens at all.

The Pre-fill field rule avoids this:

|                        | Pre-fill field rule                        | Jira default value   |
| ---------------------- | ------------------------------------------ | -------------------- |
| **Scope**              | Per UIM context (space + work type + view) | Per field context    |
| **Conditions**         | Supports user, group, and field conditions | None                 |
| **Transition screens** | Yes                                        | No                   |
| **Option duplication** | Not required                               | Required per context |

Conditional, context-aware defaults require a UI Modifications app like Field Rules or a scripting app.

See [Field Rules vs native Jira](https://docs.forgappify.com/field-rules/jira-administrator/field-rules-vs-native-jira.md) for the full comparison across every rule.

***

## Difference from Change field value

|                             | Pre-fill field                             | Change field value                         |
| --------------------------- | ------------------------------------------ | ------------------------------------------ |
| **When it runs**            | Once, when the screen loads                | Each time the user changes a watched field |
| **Preconditions required**  | Optional                                   | At least one field precondition required   |
| **Supported on Issue View** | No                                         | Yes                                        |
| **Typical use**             | Static defaults, transition pre-population | Reactive updates based on user input       |

Use **Pre-fill field** to seed a value before the user sees the form. Use **Change field value** to update a field in response to what the user is doing.

***

## Supported fields

The JSM Agent views behave like their standard equivalents.

| Field type        | Global Issue Create | Issue Transition | JSM Request Create |
| ----------------- | ------------------- | ---------------- | ------------------ |
| Assignee          | Yes                 | Yes              | No                 |
| Affects versions  | Yes                 | Yes              | No                 |
| Cascading select  | Yes                 | Yes              | Yes                |
| Checkboxes        | Yes                 | Yes              | No                 |
| Components        | Yes                 | No               | No                 |
| Date picker       | Yes                 | Yes              | Yes                |
| Date time         | Yes                 | Yes              | Yes                |
| Description       | Yes                 | Yes              | Yes                |
| Due date          | Yes                 | No               | Yes                |
| Fix versions      | Yes                 | Yes              | No                 |
| Issue type        | Yes                 | Yes              | No                 |
| Labels            | Yes                 | Yes              | Yes                |
| Multi select      | Yes                 | Yes              | Yes                |
| Multi user picker | Yes                 | Yes              | No                 |
| Number            | Yes                 | Yes              | Yes                |
| Original estimate | No                  | Yes              | No                 |
| Paragraph         | Yes                 | Yes              | Yes                |
| Parent            | Yes                 | Yes              | No                 |
| People            | Yes                 | No               | No                 |
| Priority          | Yes                 | Yes              | Yes                |
| Project picker    | Yes                 | Yes              | No                 |
| Radio buttons     | Yes                 | Yes              | No                 |
| Reporter          | Yes                 | Yes              | No                 |
| Resolution        | No                  | Yes              | No                 |
| Select            | Yes                 | Yes              | Yes                |
| Summary           | Yes                 | Yes              | Yes                |
| Target end        | Yes                 | No               | No                 |
| Target start      | Yes                 | No               | No                 |
| Text field        | Yes                 | Yes              | Yes                |
| URL               | Yes                 | Yes              | No                 |
| User picker       | Yes                 | Yes              | Yes                |

***

## Limitations

* **Issue View is not supported**, including the JSM Agent view. To update a field reactively on Issue View, use [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md) instead.
* **Project role conditions are not supported on JSM Request Create.** User conditions based on project roles are ignored when the rule runs on the portal. Use group-based conditions instead.

***

## Related rules

* [Change field value](https://docs.forgappify.com/field-rules/rules/change-field-value.md) - update a field reactively when the user changes another field.
* [Lock field](https://docs.forgappify.com/field-rules/rules/lock-field.md) - lock a field after pre-filling it so users cannot change the value.
* [Show field](https://docs.forgappify.com/field-rules/rules/show-field.md) - show or hide a field based on conditions.
* [Make field required](https://docs.forgappify.com/field-rules/rules/make-field-required.md) - make a field mandatory based on conditions.
