Check out what’s new for ScriptRunner for Jira Server.

6.14.0

When using the single or multiple issue picker fields, you can now find issues by a query on the issues that they link to. See the issuePickerField function for more information.

Storing Environmental Variables

Want to simplify migrating from a test instance to production? Check out our new Storing Environmental Variables documentation for best practices.

New Features

  • SRJIRA-4827 - You can now search for Issue Picker field values by Issue Summary.

Bug Fixes

  • SRPLAT-1364 - Script Editor failed to open files with national characters created on 6.11.0.

  • SRJIRA-4839 - We fixed a bug where invalid format errors did not appear in Edit screen when scripted fields were present.

  • SRJIRA-4836 - An issue causing the script file to disappear from the UI for REST Endpoint scripts has been fixed.

  • SRJIRA-4826 - We fixed a bug where under certain circumstances a bulk move failed.

  • SRJIRA-4822 - We fixed a problem where if you added or edited a resource, a failure in another resource could prevent refreshing.

  • SRJIRA-4792 - The hasLinkType JQL function no longer breaks JSD queues when the referenced link type is renamed.

  • SRJIRA-3751 - We fixed a problem where filters using date/time methods with the expression JQL function, would intermittently fail.

6.13.1

Bug Fixes

  • SRJIRA-4852 - We fixed a problem where a javascript error could prevent certain other plugins displaying correctly.

6.13.0

New Features

  • SRJIRA-4794 - Database Picker fields now use the Display Value instead of ID in email notifications.

Bug Fixes

  • SRPLAT-1345 - Audit logging was added for Settings changes.

  • SRPLAT-1302 - Secure shell options have been expanded to include boolean literals and negation.

  • SRJIRA-4821 - A bug causing Issue Picker and Database Picker fields to copy the value to the left of the cell, when no value was present in the issue navigator, has been fixed.

  • SRJIRA-4529 - Fields set as read-only in a behaviour initialiser are now correctly prevented from being edited inline.

  • SRJIRA-3783 - The Behaviours setRequired method for the Tempo Account and Teams field no longer allows you to submit the value None.

  • SRJIRA-2230 - The post function Assign to Last Role Member now correctly picks the previously assigned user from the specified role.

6.12.0

Potentially Breaking Change

Previously, you could enable sorting in JQL queries through the use of the getSortValue closure and sortAttribute property in Database and LDAP pickers respectively.

These are now redundant. If you had implemented these, and don’t make any changes, the sort order may not be what it was before upgrading. Assuming you want the default value to be indexed and to be used for sorting, it’s safe to remove them. Otherwise, see the new configuration options at Database Picker or LDAP Picker.

New Features

  • SRJIRA-3852 - We now index Database Picker fields on display value.

Bug Fixes

  • SRPLAT-1221 - Bitbucket/Confluence/Jira is no longer prevented from correctly shutting down when ScriptRunner is installed.

  • SRJIRA-4779 - The Behaviours feature now scrolls to fields in errors on submit, for all types of fields.

  • SRJIRA-4759 - We fixed a problem where it was not possible to stop watching an issue after the Add Watcher post function triggered.

  • SRJIRA-4755 - We fixed a problem where Database Picker field values were not saved if you left inline edit active while creating a new issue in a modal window.

  • SRJIRA-4747 - The behaviour to clear the value of a selection list field now works in JSD portal.

  • SRJIRA-4735 - There is no longer a NullPointerException on Pie Chart gadgets using Scripted Issue Picker custom fields.

  • SRJIRA-4724 - JiraProjectPicker now returns projectId as an immutable project identifier.

  • SRJIRA-4623 - The Database Picker field can now set the field’s value using setFormValue on Jira Service Desk.

  • SRJIRA-2191 - Split Custom Field Contexts built-in script now works properly for a cascading select list.

6.11.0

A new feature-length tutorial has been added on using the database picker with a raft of customisations, based on a real external database running in a docker container. Take a look at the Country Picker tutorial.

In ScriptRunner 7 there will be potentially breaking changes for users of the Database Picker - see breaking changes.

New Features

  • SRJIRA-4707 - You can now search for a lower case issue key in the Issue Picker field.

  • SRJIRA-2563 - We now support using behaviours with Mindville Insight custom fields.

Bug Fixes

  • SRPLAT-1319 - Custom scripts returning String from getHelpUrl() did not work.

  • SRJIRA-4719 - renderColumnHtml closure is no longer called with wrong parameters.

  • SRJIRA-4710 - Clone Plus for Jira add-on now works for issues with Issue Picker fields.

  • SRJIRA-4699 - Dynamic forms ProjectRolePicker now persists data correctly.

  • SRJIRA-4696 - LDAP Picker fields now have their values automatically html-encoded.

  • SRJIRA-4690 - Database Picker fields no longer cause an exception in Issue Search.

  • SRJIRA-4688 - There is no longer an error when moving an issue without an Issue Picker field to an issue type with an Issue Picker field.

  • SRJIRA-4686 - Database Picker fields can now be sorted by clicking the column header in the issue navigator.

  • SRJIRA-4638 - Behaviour page no longer fails to load with the Cannot read property 'scriptPath' of undefined error.

  • SRJIRA-3937 - There are no longer hidden lines in the Script Editor

  • SRJIRA-2867 - Show parent issue in hierarchy Script Field no longer breaks when target issue has a parent.

  • SRPLAT-1302 - We have expanded secure shell options to include boolean literals and negation.

  • SRPLAT-1313 - Script configurations can now be saved with a blank inline script.

6.10.0

Ceasing Development on Jira 7

We are no longer developing new features for ScriptRunner versions running on Jira 7. See our Jira 7 Development statement for more information.

Bug Fixes

  • SRJIRA-4681 - Jira agile functions such as previousSprint and nextSprint fail in a safe way when security is overridden.

  • SRJIRA-4670 - Picker fields no longer incorrectly sanitise the entirety of the "view html", rather than just DB or LDAP record.

  • SRJIRA-4662 - firstCommented and lastCommented fields available in the dateCompare() jql function comparison expression now work as expected.

  • SRJIRA-4649 - Webhooks that use previousSprint in their JQL query no longer fail with a NullPointerException.

  • SRJIRA-4611 - Issue Picker required fields now register a valid selection correctly.

  • SRJIRA-4598 - Behaviours mapping to a selected issue type is now working correctly.

  • SRJIRA-4412 - IssueLinkCreatedEvent and IssueLinkDeletedEvent are no longer triggered when the project is not included in the listener’s Project field.

  • SRJIRA-3634 - Script listeners that react to ProjectComponent -based events now take the Project field into account.

6.9.1

Bug Fixes

  • SRJIRA-4672 - lastUpdate() issue function was not working correctly for issues without comments in ScriptRunner 6.9.0.

6.9.0

New Features

  • SRJIRA-4501 - The workflow error output was improved to make it easier to find the workflow and transition where the script is configured.

Bug Fixes

  • SRJIRA-4596 - Indexing failed because the sr_num_atch field was sometimes added multiple times per index document in Jira 8.10+.

  • SRJIRA-4586 - Compatibility with Jira 8.12 was added.

  • SRJIRA-4332 - Behaviours were not highlighting a tab when a field is required.

  • SRJIRA-4270 - Selecting or unselecting the All option from the Custom Fields cog caused the value set in the Read Only Single Select List to reset to None even by users who have limited access.

  • SRJIRA-4121 - LDAP and the database picker did not work when when the custom field context contained issue types. Additionally, the pickers were fixed for Service Desk users.

  • SRJIRA-4021 - Inline edit was not disabled by behaviours when it should have been on the Issue Details page for Jira 8 for certain board pages.

  • SRJIRA-3563 - The Bulk Copy SLA broke automation rules with "SLA time remaining" in a WHEN statement.

6.7.0

Retiring Support for Internet Explorer

From Feburary 1st 2021 ScriptRunner will no longer support Internet Explorer. See our full statement for more information.

New Features

  • SRJIRA-4527 - Text search now looks for a match of the entire string first in Issue Picker fields.

  • SRJIRA-4449 - Issue Picker script fields now display up to 30 preview issues.

  • SRJIRA-4160 - You can now store all environment-specific variables.

Bug Fixes

  • SRJIRA-4590 - The information logged in the Indexing Stats Performance report has been improved.

  • SRJIRA-4578 - Picker fields have been made stattable to allow them to appear in certain gadgets.

  • SRJIRA-4576 - You can now update the SQL in Database Picker fields.

  • SRJIRA-4573 - You can now change the display attribute in LDAP Picker fields.

  • SRJIRA-4488 - DiagnosticsLoggerManager is compatible with com.atlassian.logging.log4j.layout.JsonLayout on Jira 8.

6.6.0

Customising Database and LDAP Pickers

You can now customise LDAP and database pickers using the Configuration Script option. Use this to customise the displayed value, add additional information to the picker drop-down, customise the search filter, and more. For examples of these and more information on how you can use this functionality, see our Database Picker and LDAP Picker documentation.

Ability to Disable Switch User Built-in Script

The Switch User built-in script allows administrator users to temporarily assume the identity of another user.

This script is enabled by default. However, if you have extremely strong compliance requirements, you may wish to disable this feature.

This release adds a toggle to the Settings tab to disable the Switch User built-in script. When the script is disabled, it is not accessible for any user (including system administrators).

For more information, see the Disable Switch User Built-in Script documentation.

New Features

  • SRJIRA-4500 - Behaviours can now be enabled/disabled independently. Actions related to each behaviour have been moved into the Cog menu.

  • SRJIRA-3996 - Database Picker field queries can be generated using attributes of the current issue.

Bug Fixes

  • SRPLAT-1228 - An issue causing parameters to be garbled when adding a project filter to a query containing a picker field has been fixed.

  • SRPLAT-1227 - Some documentation links were missing from scripts.

  • SRPLAT-1217 - Switch to Different User script banner no longer breaks TinyMCE 4 functionality.

  • SRJIRA-4543 - Database Picker values are now sortable in JQL queries.

  • SRJIRA-4521 - ScriptRunner javascript was incompatible with the Microsoft Azure Active Directory single sign-on for JIRA plugin.

6.5.0

Bug Fixes

  • SRPLAT-1213 - Test on borrow is now the default for LDAP connections.

  • SRJIRA-4509 - Script fields now work correctly on Jira Service Desk when there are multiple request types corresponding to the same issue type.

  • SRJIRA-4463 - Script Fragment errors now logs information users can use to find the broken fragment.

  • SRJIRA-4418 - Behaviours no longer overwrite other behaviour scripts.

  • SRJIRA-3366 - The View in Issue Navigator button has been updated to show the correct results.

  • SRJIRA-4517 - ScriptRunner is now compatible with Jira 8.11.

  • SRJIRA-4451 - javax.mail.Session creation no longer fails in Jira 8.10.0.

6.4.0

JQL function: memberOfRole

Use memberOfRole to find issues where the value of a user field is a member of a given role, for example:

issueFunction in memberOfRole("Reporter", "Administrators")
issueFunction in memberOfRole('Approvers', 'Service Desk Team')

See our documentation on memberOfRole.

New Features

  • SRJIRA-4349 - You can now create an LDAP resource with Anonymous bind.

  • SRJIRA-4271 - A JQL function has been added to find issues assigned to users in a role.

Bug Fixes

  • SRPLAT-11 - An invalid user-configured raw XML script fragment could have prevented the ScriptRunner plugin from enabling.

  • SRJIRA-4405 - The lastComment("inRole Administrators") query has been optimised to take account of any project clauses.

  • SRJIRA-4388 - We fixed an issue in behaviours where the Method Selection field was not appearing, even though a file had been selected.

  • SRJIRA-4353 - The behaviour UI condition now checks the workflow step correctly for the Create Issue screen.

  • SRJIRA-3799 - In behaviours, the IssueType/Project field is no longer editable via the Create Issue screen when the Behaviour sets it to read-only.

  • SRJIRA-3766 - A Field Required error in behaviours has been fixed.

6.3.0

New Features

  • SRJIRA-2563 - We added support for using Behaviors with Mindville Insight custom fields.

Bug Fixes

  • SRPLAT-1171 - The Confluence-specific scriptMacroMetadataProvider module no longer shows up in UPM for all ScriptRunner products.

  • SRJIRA-4401 - There is no longer a NullPointerException when a JQL function is unavailable.

  • SRJIRA-4391 - Adding a default value to a database picker no longer causes a MethodInvocationException.

  • SRJIRA-4386 - Multi-Issue Picker field validation now works correctly when the field is set to Required using the Field Configurations.

  • SRJIRA-4323 - Picker fields are now fully functional when placed at the bottom of a form.

  • SRJIRA-4076 - The behaviour "Setting a Default Description" now works correctly when the Rich Text Editor is disabled.

  • SRJIRA-3918 - Setting a user picker value via behaviours now works in JSD portal if the logged-in user is a customer.

  • SRJIRA-2974 - Aggregate functions were not always displaying calculations when a search was performed.

6.2.1

Bug Fixes

  • SRJIRA-4380 - The clearError behaviour was not able to clear out setError.

  • SRJIRA-4374 - AddMissingScriptFieldConfigurationsUpgradeTask skipped custom fields.

  • SRJIRA-4373 - The ScriptRunner plugin presence broke the JSD Customer Portal loading.

6.2.0

Bug Fixes

  • SRJIRA-4338 - When using two select2 fields with behaviours on each, it was possible to get an infinite loop.

  • SRJIRA-4112 - When using behaviours to change options on a checkbox or radio button, field-level scripts did not run because change events were not fired.

  • SRJIRA-4032 - The setRequired behaviour method on User Picker fields could prevent the User Selection drop-down from clearing.

  • SRJIRA-2686 - When using behaviours, clearing all radio button/checkbox options prevented being able to add options.

  • SRJIRA-2416 - Behaviours did not return the value of the Sprint field as expected.

6.1.0

New Features

  • SRJIRA-4329 - There is now IssueContext-like access to request type name in Service Desk behaviours.

Bug Fixes

  • SRPLAT-1139 - Compilation failures in one script caused entire features to fail.

  • SRPLAT-1131 - You now have the ability to set all Hikari pool configuration parameters when using database connections.

  • SRPLAT-1094 - Autocompletion requests failed when requesting autocomplete after typing "Check".

  • SRJIRA-4334 - Making a multi-group picker read-only now disables the link to an external popup.

  • SRJIRA-4308 - The type of issue in post-function was incorrectly Issue and not MutableIssue.

  • SRJIRA-4294 - Database picker fields now use the correct RestFieldOperationsHandler.

  • SRJIRA-4280 - Single-select list fields width is no longer narrow when ScriptRunner is installed.

  • SRJIRA-4263 - Behaviours now works correctly with Chrome 81.0.4044.92+.

  • SRJIRA-4260 - Classloader cache now refreshes properly.

  • SRJIRA-4177 - Database Picker and Issue Picker fields configured for "Multiple" selection are now correctly "Required" when set to "required" via field configuration.

  • SRJIRA-4170 - The Multiple Issue Picker no longer shows an entry in the Change History of an issue when it was not changed.

  • SRJIRA-4159 - 5.6.15 no longer throws a java.lang.ClassCastException error when using an LdapTemplate.

  • SRJIRA-4027 - An issue with keyboard shortcuts and autocomplete in the browser-based Code Editor has been fixed.

  • SRJIRA-3973 - Post function "Transition parent when all subtasks are resolved" does not require a Resolution field.

  • SRJIRA-3934 - The setLabel() no longer causes a duplicate if any markup parameters are included.

  • SRJIRA-3860 - The script for reindexing scripted fields in the documentation has been updated for the Jira 8 API.

  • SRJIRA-3771 - Single-select / Multi-select list conversion no longer duplicates field (Behaviour) on Jira Service Desk Customer Portal.

  • SRJIRA-3720 - Behaviours API now recognises translated language.

  • SRJIRA-3526 - User Picker Required validation now works correctly for behaviours.

  • SRJIRA-3367 - The User-aware and Date-aware script fields now appear in the correct panel after a cache reset.

  • SRJIRA-3303 - Issue picker field now works correctly as a required field.

  • SRJIRA-2820 - The Bulk Fix Resolution built-in script now closes the SLA of the issue.

  • SRJIRA-2535 - The Bulk-Fix-Resolution built-in script now retains the original resolution date.

  • SRJIRA-2027 - Form values are now available in the Behaviours initialiser.

6.0.2

Bug Fixes

  • SRJIRA-4325 - Script Field - Configure screen link is broken

  • SRJIRA-4318 - Unable to create ticket issue upgrading to 6.0.1 due to missing script field config

6.0.1

Bug Fixes

  • SRPLAT-1119 - Classes in scriptrunner-api/spi no longer consumable by dependent plugins

  • SRJIRA-4297 - Built in script Script registry - java.lang.NullPointerException

  • SRJIRA-4295 - Exceptions during issue creation, indexing due to failed script fields upgrade

6.0.0

Groovy Upgrade

The version of Groovy used by ScriptRunner has been upgraded from 2.4.15 to 2.5.11. Improvements and new features (like additional AST transformations, or the new tap() method) shipped in Groovy 2.5 are now available to ScriptRunner users. See the Groovy 2.5 Release Notes for more information.

As with any dependency upgrade, breaking changes could potentially affect users' scripts. However, the breaking changes between Groovy 2.4 and 2.5 are relatively minor. The low-level nature of most of these breaking changes means they are unlikely to impact many ScriptRunner scripts if any.

Take a look at the list of breaking changes in the Groovy 2.5 Release Notes for further details.

IntelliJ Removal

This version removes all support for the IntelliJ IDEA plugin. See our previous deprecation announcement for our rationale and plans for the future.

Hidden Fields Removal

Hidden Fields custom fields, which were deprecated in version 5.6.14, have now been removed.

Please review the documentation for converting them to regular Jira fields, and other alternatives.

Use of Natural Searchers in Script Fields

Previously many users may have used the Natural Searchers for Jira plugin. Use of these searchers on script fields allows the use of gadgets such as Two Dimensional Filter Statistics and Heatmap, for these fields.

This release of ScriptRunner includes searchers similar to those provided by the Natural Searchers for Jira plugin. On installation of this version, ScriptRunner converts any usage of searchers in script fields from the plugin versions, to ScriptRunner-native versions.

If you are only using this plugin for script fields natural searchers, you can uninstall the Natural Searchers for Jira_ plugin. To check your usage of the Natural Searchers for Jira plugin navigate to *Admin → Natural Searchers.

Please see the warning message on usage.

New Features

  • SRJIRA-2335 - ScriptRunner now provides stattable/natural searchers.

Bug Fixes

  • SRPLAT-1092 - There is now DocLink support for absolute URLs.

  • SRPLAT-1084 - The autocompletion window of the Script Console now closes correctly.

  • SRPLAT-1041 - ScriptRegistry performance has been improved.

  • SRJIRA-4075 - The Custom Email post function now saves multiple values selected in To Issue Fields and CC Issue Fields.

  • SRJIRA-3080 - The binding variable 'originalIssue' is no longer incorrectly displayed for Custom Script post functions.

Have questions? Visit the Atlassian Community to connect, share, and learn with other Atlassian users and experts, including Adaptavist staff.

Ask a question about ScriptRunner for JIRA, Bitbucket Server, or Confluence.

Want to learn more? Check out courses on Adaptavist Learn, an online platform to onboard and train new users for Atlassian solutions.