Release 6.16.x

6.16.0

 

New ScriptRunner Action for Automation for Jira

Automation for Jira has released a new API for third-party integrations. This allows us to provide some requested enhancements, such as the ability to retrieve the initiator of the action, and the ability to use smart values. We have also added the ability to use dynamic forms.

Because the API was so different, we have decided to provide a new action and deprecate the original one. If you need the new action, copy your script from the old action to the new, and remove the old one.

Read more in our documentation on Automation for Jira.

Workflows Tab

You can now view, edit, delete and disable/enable ScriptRunner workflow functions from the Workflows tab. We have also made it easier to create a new ScriptRunner workflow function, by adding this functionality to the Workflows tab. See our workflow functions documentation for more information.

New features

  • SRJIRA-4806 - You can now use smart values in the Execute a ScriptRunner script action.

  • SRJIRA-3621 - We now support >= operators in the dateCompare JQL function.

Bug fixed

  • SRPLAT-841 - The URL of the Endpoint-scanning endpoint is now correctly mapped to the backend method.

  • SRJIRA-4907 - Database Picker fields no longer change to show the internal ID instead of the selected value after a comment is added from the service desk portal.

  • SRJIRA-4900 - The Automation for Jira integration now provides two actions. The new action makes use of the updated Automation for Jira API

  • SRJIRA-4895 - Script fields upgrade tasks no longer fail if there is data in a newer format.

  • SRJIRA-4891 - Using key combinations to select all script text and then pressing delete, now works within behaviour script editor sections.

  • SRJIRA-4882 - The currentUser binding variable in Automation for Jira is no longer null when the Actor username has been renamed.

  • SRJIRA-4801 - You can now copy SLAs for service desk projects using Copy Project.

  • SRJIRA-4220 - In the case of a StackOverflowError during the manual execution of a job, the user is now informed on how to solve the issue.

  • SRJIRA-4126 - There is no longer a String index out of range error when clicking on links in Script Registry page.

  • SRJIRA-4125 - setHidden,setLabel,setDescription now work for the behaviours Attachment field on the service desk portal.

  • SRJIRA-4074 - Heritage listeners can now be referred to by file path.

  • SRJIRA-3465 - UserMessageUtil.error method now displays the error message correctly for inline field edits or edits from the Boards page.

On this page