Field Behaviour Limitations
Understand the platform limits, supported views, space types, and field considerations that affect how field behaviours save and run.
Field behaviours are powered by Atlassian's UI Modifications API on the Forge platform. Because of this, field behaviours are subject to limits set by Atlassian, as well as some additional considerations outlined below.
API limits
These are hard limits imposed by Atlassian's platform. Exceeding them will prevent your field behaviour from saving or deploying correctly.
| Limit | Value |
|---|---|
| Maximum number of field behaviours per app | 3,000 |
| Maximum number of contexts per field behaviour | 1,000 |
| Maximum script size per field behaviour | 50,000 characters |
You can find further information in Atlassian's UI Modifications guide and Jira Cloud platform REST API.
Contexts
A context is a unique combination of space, work type, and view. For example, a field behaviour configured for 3 work types and 2 views has 6 contexts. For more details on how contexts are calculated, see supported fields and products.
On a service desk space, the request type is also part of the context. A behaviour that applies to several request types creates a context for each one, so it reaches the 1,000 context limit faster than the example above suggests.
Other considerations
Performance
Complex scripts may run more slowly than simple or efficient ones. If your field behaviour is noticeably slow, consider simplifying the script logic.
Supported views
Field behaviours can be applied to the Create, Work item, and Transition views. Not all fields are supported in every view. See supported fields and products for the full breakdown.
Field behaviours mapped to the transition view only run if your Jira instance has Atlassian's new issue transition experience enabled. On some instances this is not enabled, and where it is not, the field behaviour is saved and valid but does not run, and no error is shown. So if a transition view behaviour appears to do nothing, first check whether this experience is enabled on your instance. If it is not enabled, raise a support ticket with Atlassian asking them to turn on the new issue transition experience for your site.
Supported space types
Both company-managed and team-managed Jira spaces are supported. However, business spaces (a subset of team-managed spaces) support the Create view only.
Space and work type wildcards
You cannot select all spaces and all work types simultaneously. For more details, see supported fields and products.
System fields and custom fields
Some Jira-native system fields can also exist as custom fields of the same type. For example, Labels is a Jira-native system field, but you can also create a custom field of type Labels. Field behaviours only support Jira-native system fields, so they may not work as expected on custom fields of the same type. See supported fields and products for a full list of supported fields.