Pre-fill field
The purpose of the rule is to pre-fill a field when the screen loads.
On Issue Transition, the field is pre-filled only if it was empty before the screen loads. To change this behaviour, enable the relevant setting:
The rule can run conditionally based on user roles , groups individuals, or field values set before its execution.
Default Value Configuration vs. UI Modification
Default Value Configuration (out-of-the-box)
Default values can be configured directly within the system.
In Custom fields configuration → Contexts and default value, you can set a default value for a field.
If different values are required for different issue types, you can create additional contexts and set default values for each.
Limitations
This approach works well for custom fields without options. However, when creating a new context, all options and settings must be configured from scratch.
Maintaining multiple contexts leads to duplicate option lists, increasing complexity and maintenance efforts.
Why Use UI Modification?
UI Modification provides a more flexible alternative to setting default values.
Advantages
✅ Avoids duplicating options across multiple contexts.
✅ Allows setting different default values based on user roles, groups, or other fields.
✅ Enables pre-filling values on transition screens.
Use cases
Pre-fill fields on Create Issue screen for selected issue types
Configuration steps:
Create a separate UI Modification for each issue type or group of issue types.
Set the View types to Global Issue Create.
Add a Pre-fill field rule for each field you want to prepopulate.
Last updated