See this in action in our Sanbox https://radbee-sandbox.atlassian.net

Integration: Including ScriptRunner Scripted Fields In Jira Snapshots

Owned by Rina Nir _RadBee
Last updated: Jun 25, 2024
1 min read

This is obsolete!

ScriptRunner scripted fields are now supported as any other custom field and special configuration is not needed.

For older Snapshots who use the old configuration of ScriptRunner scripted fields:

What to do?

  1. The old data is not impacted

  2. If you need to take a new Snapshots on that page, you'll need to edit the configuration of the macro. Remove the existing column, and re-add that field.





Jira Snapshots for Confluence can incorporate ScriptRunner scripted fields in the Snapshots.

Refer to the ScriptRunner user manual for information about how to configure scripted fields in Jira Cloud.

Due to the architecture of Jira Cloud and the ScriptRunner app, ScriptRunner scripted fields are not recognized by Jira, and cannot be retrieved through the integration link with Jira.

We’ll take you through the steps to have Jira Snapshots recognise these fields. Once this is done, the fields will be available for Snapshots.

See an example use case here: ScriptRunner Scripted Fields in Jira Snapshots

Steps to Follow

 

  1. In your Jira instance:

    1. Navigate to the Jira instance from which Snapshots will be fetched, accessing as an admin user.

    2. Navigate to the Scripted Fields configuration screen.

    3. Note the Field Name and Field Identifier of each field you want to make available to Snapshots.

  2. Back in Confluence, navigate to the Confluences admin area, and select Atlassian Marketplace / Jira Snapshots for Confluence.

    1. Under the ScriptRunner fields tab, add the identifier and name of each field.

    2. Click Add Field.

You're all set! Now when configuring a Jira Snapshot, you’ll be able to select these fields as columns in the report.