ScriptRunner Migration Suite Changelog

You can now export the results of the ScriptRunner Migration Analyse and Assess Tool in a PDF to share with stakeholders to aid in your migration. 

When deploying workflow post functions or validators, you can control their placement among other workflow functions by using a placement block on a ScriptRunner rule. Supported placement fields are: 

• index (0-based absolute position)
• first
• last

You can see an example in the SMS Example Project. 

There is a known bug on the authentication step of working with the Dev and Deployment Tool. The automatic browser-based authentication is currently broken in Google Chrome and browsers based on Chromium. We're working on it, but there are some blockers. Please bear with us!

Check out our new SMS Web App AI Training and Usage guide for detailed information about the AI models used, AI-generated content, and evaluating AI output. 

You can now use Jira Space Keys (like ECO, CONFCLOUD) and Work Item Type names (like Task, Story, and Bug) for Behaviours configurations in the ScriptRunner Dev and Deployment Tool. 

To see this change, update your migration-settings plugin to version 0.2.0 in the example project's settings.gradle, as shown on line 28 in the image below. 

A bug affecting workflows in the Dev and Deployment Tool was fixed.

The following error appeared when updating workflow scripts while deploying in the Dev and Deployment tool: 

Unexpected response from workflow update validation (400): {"errorMessages":["payload.workflows[0].transitions[0].actions[0].parameters : parameter values must be less than 32768 characters"],"errors":{}}

Although the bug is fixed, you will probably need to re-deploy your workflows with the latest version of the Dev and Deployment Tool.

If you’re still getting errors, look for a workflow post function (or "action") in your workflow that doesn’t load in the UI when you try to edit it.

The error usually occurs when the unique identifier used by the workflow function was changed after deploying it, leaving an orphaned configuration that older versions of the plugin could accidentally corrupt. This corruption won’t happen in the latest version, but the old workflow function may still be there in need of removal.

If you have post functions that won’t load in the workflow editor UI (shown below), the easiest workaround is to delete them from your workflow and redeploy from the Dev and Deployment Tool with the latest update.  

Support has been added for the following features in the ScriptRunner Migration Analyse and Assess Tool: 

• Behaviours
• Scripted Fields

Updates to the ScriptRunner Migration Analyse and Assess Tool include:  

• Ensures CRON expressions are not set for more than an hour to adhere to Cloud limitations. 
• Analyses configurations with multiple scripts (for example, a listener with a main script and conditions). 
• Check for duplicate scripts that are exact matches across all configurations. 
  

  If you participated in EAP, please re-import exports to see duplicate script metrics.