Scripted Fields

What are Scripted Fields?

You can use ScriptRunner for Jira Cloud's Scripted Fields to customise how the information for an issue is displayedThey enable you to display information that would otherwise be unavailable for an issue by calculating or amalgamating data from one or more existing fields. Check out our examples for more details.

Scripted Fields appear when you assign their associated custom fields to your screen.

Add-on User

All scripted fields are executed as the add-on user.

How to use Scripted Fields

Currently, scripted field results are only updated when viewing an issue. Please keep this in mind when using scripted fields as part of JQL filters.

Scripted Fields are a type of calculated field, so you can display a calculated custom field using ScriptRunner scripts that run when an issue is viewed. It's good practice to keep the scripts as simple as possible so as to reduce loading time. 

Scripted Fields work by using the same process as other scripts, such as Script Listeners, where you write code that executes REST API calls to either the Jira Cloud Rest API or your own external REST API call.

Take our ScriptRunner Tour to help you get started with Scripted Fields and gain access to helpful videos and demos. You can also check out the demo video on the Example Scripted Fields page.

Before you start

Visit Atlassian's documentation to learn about the Jira Cloud REST API.

Broaden your horizons by exploring the Adaptavist Library for Scripted Field examples.

Create a Scripted Field

  1. Navigate to ScriptRunner → Scripted Fields.
    Depending on whether or not you have already created scripted fields, you are presented with either a landing screen or a list of the previously created scripted fields.

  2. Click Create Scripted Field from the initial landing screen if none have been previously created. If you would prefer to make use of our built-in examples, click Add Examples to add two scripted field examples to your instance.

    Click Create Scripted Field from the previously created list.

  3. (Optional) Click Edit or Delete for your preferred scripted field via the Actions ellipsis.

  4. (Optional) Click the relevant entry in the Custom Field ID column if you want to modify the details of any of the custom fields associated with each scripted field. You are redirected to the Edit Custom Field Details screen contained within the Issues section of the Jira admin. Once edited, click Update to confirm your changes, as shown below:

  5. Enter the name of the scripted field in Field Name.
    NOTE: The Identifier field shows the unique identification key for the new scripted field.

  6. (Optional) Enter a description for the scripted field that summarises its purpose in the Description field.
  7. Select the scripted field's Field Type. Ensure you pick the correct field type for the data returned by your script. See Return Types for more information.

  8. Enter a Script to execute. This script is triggered when an issue is loaded. 

    Scripted fields in Jira Cloud do not dynamically update. The script triggers on issue load; therefore, changes to the field value are not reflected instantly, and the issue must be reloaded.

  9. (Optional) Select an issue in Test against issue to test the scripted field before saving. We recommend carrying out this step.

    Any changes to the scripted field's configuration will require a re-test.

  10. Click Save.
    Once saved, you will see a new entry in the Custom Field ID column of the scripted fields list that is associated with your newly created scripted field. If you want to modify the custom field, refer to Step 4 above. Scripted fields run only when an issue is viewed, so they must be added to a screen before it runs. To do this:

    1. Open your preferred project from the Jira admin page and click Project Settings.
    2. Navigate to Issues → Layout, where you will see the default Issue layout page.
    3. Drag the newly created scripted field anywhere within the Issue panel, click Save and return to Project Settings.
      You can now
      open any issue and view the scripted field within the layout of that issue.

Edit a Scripted Field

  1. Navigate to ScriptRunner → Scripted Fields. A list of all previously created scripted fields is shown.

  2. Click Edit on the Actions ellipsis of the scripted field you wish to edit. The following screen is displayed:

  3. Edit the fields as required.

    Limited edits for Scripted Fields

    There are limits to the changes that can be made here because a custom field has already been created for the scripted field you are editing. If you want to change the Field Name or Description, you need to navigate to the Jira administration section. Also, you must create a new scripted field in ScriptRunner if you want to change the Field Type.

  4. Click Save after all changes are complete. You can also click Revert to undo those changes

Return Types

The script for your field must return the correct data type.

For a text field, the script must return a single line String. The String returned must be no more than 255 characters and must not contain any newline characters. If you want to return a string of more than 255 characters, you should use a paragraph scripted field.

// This is OK return "Hello World" // This is not OK return "Hello\nWorld"

For a number field, the script must return a numeric type, for example an Integer, Long, Float, Decimal, or BigDecimal.

For a date field, the script must return a LocalDate.

import java.time.LocalDate import java.time.Month return LocalDate.of(2020, Month.JUNE, 25)

For a datetime field, the script must return a ZonedDateTime.

import java.time.LocalDate import java.time.LocalTime import java.time.Month import java.time.ZonedDateTime import java.time.ZoneId import java.time.ZoneOffset return"America/New_York")) // or return ZonedDateTime.of(LocalDate.of(2020, Month.JUNE, 25), LocalTime.of(13, 45, 0), ZoneOffset.ofHours(-3))

For a paragraph field, you can return either plain text or rich text.

You can use plain text if you want to return a single line string of more than 255 characters. You cannot include newline characters in a plain text string.

If you return using rich text, you must use the Atlassian Document Format (ADF). You can refer to Atlassian's ADF Builder for further details. You can also watch our demo video showing how to display tables within scripted fields using rich text.

We've provided some ADF examples below:

  • table with headings, 2 rows and 2 columns
[ "version": 1, "type": "doc", "content": [ [ "type": "table", "attrs": [ "isNumberColumnEnabled": false, "layout": "default", "localId": "58c619ab-f32c-4dfa-aa54-2b4b39643deb" ], "content": [ [ "type": "tableRow", "content": [ [ "type": "tableHeader", "attrs": [:], "content": [ [ "type": "paragraph", "content": [ [ "type": "text", "text": "Header 1" ] ] ] ] ], [ "type": "tableHeader", "attrs": [:], "content": [ [ "type": "paragraph", "content": [ [ "type": "text", "text": "Header 2" ] ] ] ] ] ] ], [ "type": "tableRow", "content": [ [ "type": "tableCell", "attrs": [:], "content": [ [ "type": "paragraph", "content": [ [ "type": "text", "text": "Row 1 Column 1" ] ] ] ] ], [ "type": "tableCell", "attrs": [:], "content": [ [ "type": "paragraph", "content": [ [ "type": "text", "text": "Row 1 Column 2" ] ] ] ] ] ] ], [ "type": "tableRow", "content": [ [ "type": "tableCell", "attrs": [:], "content": [ [ "type": "paragraph", "content": [ [ "type": "text", "text": "Row 2 Column 1" ] ] ] ] ], [ "type": "tableCell", "attrs": [:], "content": [ [ "type": "paragraph", "content": [ [ "type": "text", "text": "Row 2 Column 2" ] ] ] ] ] ] ] ] ] ] ]

When you are in issue view, this table example appears as follows:

  • paragraph
[ "version": 1, "type": "doc", "content": [ [ "type": "paragraph", "content": [ [ "type": "text", "text": "This is a paragraph" ] ] ] ] ]

When you are in issue view, this paragraph example appears as follows:

JSON notations

Atlassian’s Document Format Builder outputs JSON, so if you want to use it directly in the console rather than converting it to Groovy, you can use new groovy.json.JsonSlurper().parseText("""Your ADF"""). See the example below:

return new groovy.json.JsonSlurper().parseText(""" { "version": 1, "type": "doc", "content": [ { "type": "table", "attrs": { "isNumberColumnEnabled": false, "layout": "default", "localId": "58c619ab-f32c-4dfa-aa54-2b4b39643deb" }, "content": [ { "type": "tableRow", "content": [ { "type": "tableHeader", "attrs": {}, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "Header 1" } ] } ] }, { "type": "tableHeader", "attrs": {}, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "Header 2" } ] } ] } ] }, { "type": "tableRow", "content": [ { "type": "tableCell", "attrs": {}, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "Row 1 Column 1" } ] } ] }, { "type": "tableCell", "attrs": {}, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "Row 1 Column 2" } ] } ] } ] }, { "type": "tableRow", "content": [ { "type": "tableCell", "attrs": {}, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "Row 2 Column 1" } ] } ] }, { "type": "tableCell", "attrs": {}, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "Row 2 Column 2" } ] } ] } ] } ] } ] } """)
On this page