Behaviours Limitations

Atlassian created an API called UI Modifications on the Forge platform, which made it possible for ScriptRunner to build Behaviours. ScriptRunner for Jira Cloud Behaviours rely upon Atlassian's UI Modifications REST API. We register UI Modifications for each ScriptRunner Behaviour, however, there are certain limitations set by Atlassian, including:

  • The number of UI Modifications (Behaviours) an app can register:
    Currently, this limit is set at 3000.

  • The number of contexts each UI Modification can have:
    This limit is set at 1000. By context, we mean project x issue type x view.

  • The number of characters in each Behaviour script:
    ScriptRunner can store up to 50,000 characters in scripts associated with a Behaviour. This includes the sum of all characters in all scripts in a single behaviour after compiling from TypeScript to JavaScript, plus our metadata. For more information, see the data in the POST request in Atlassian's documentation.

You can find further information in Atlassian's UI Modifications guide and Jira Cloud platform REST API.

Some other points worth noting about Behaviour scripts: 

  • The language used when writing the logic for Behaviour scripts is JavaScript and not Groovy. You can refer to our scripting information for more details.
  • Complex scripts may affect the speed at which your Behaviours run and may be slower than simple or efficient scripts.
  • Jira Service Management is not supported. Although Atlassian does not currently offer this functionality, we will implement it into Behaviours as soon as it is released.
  • You can apply Behaviours to the Create, Issue, and Transition views of a Jira issue. For details, refer to Behaviours Supported Fields and Products.
  • Behaviours may be applied to certain supported fields only. Not all fields are currently supported in all available views. Refer to our documentation to discover which fields are supported on each supported view.
  • Both company-managed and team-managed Jira projects support Behaviours, however, business projects (a subset of team-managed or JWM projects) support the Global Issue Create (GIC) or Create view only. Refer to Behaviours Supported Fields and Products for details.
  • You cannot select all projects and all issue types simultaneously.

  • In Behaviours, some Jira-native system fields can be custom field types. An example of this is the Labels field, which is a Jira-native system field. Only Jira-native system fields are supported, so your Behaviours may not function correctly if you have created a custom field of type Labels.

As more capabilities become available in the UI Modifications API, more functionality can be built in ScriptRunner's Behaviours feature. We are actively enhancing this feature by integrating new capabilities as Atlassian release them. 

Related content

On this page