Release 6.19.x

6.19.0

 

This version is not compatible with IE11. Do not update to this version if you use IE11. For more information see our Retiring Support for Internet Explorer page.

Bug fixed

  • SRPLAT-1442 - Fragment validation now checks for null and/or empty module keys.

  • SRPLAT-1441 - The execution history syntax highlighting was fixed.

  • SRPLAT-1434 - The Script Editor was fixed to show warning annotations. An example of a warning annotation is the usage of deprecated methods.

  • SRPLAT-1432 - The script file selector was fixed to run static type checking when a user returns to the tab.

  • SRPLAT-1431 - The Script Editor was fixed to show an overall type checking status for a given file.

  • SRPLAT-1430 - The Script Editor was fixed to run static type checking when a file is opened.

  • SRPLAT-1420 - Documentation links were corrected in the Hints and Tips.

  • SRJIRA-4984 - Links to listeners in the Script Registry now work for after disabling the listener.

  • SRJIRA-4749 - The Bulk Fix Resolutions built-in script now clears the Resolved date.

  • SRJIRA-4669 - When changing the Component/s field with behaviours, components with similar names will not be removed.

  • SRJIRA-4193 - 'setFormValue' now works on the Labels custom field.

  • SRJIRA-4182 - An issue in behaviours where an issue’s editable fields became read-only if a read-only field has been edited, has now been fixed.

  • SRJIRA-3999 - Inactive users are now filtered out when fetching email recipients from a group.

  • SRJIRA-3931 - Required fields configuration in behaviours are now correctly reflected.

  • SRJIRA-3896 - The Copy Project built-in script no longer randomises the order of service desk project request types.

  • SRJIRA-3884 - You can now set the Epic Link and Sprint field values in the initialiser when a Create Issue dialog is opened on top of the full-page Create Issue screen.

  • SRJIRA-3372 - Behaviours now make Wiki Render fields fully read-only.

  • SRJIRA-2758 - You can now get system fields with the 'getFieldByName' behaviour method.

On this page