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.