Feature Release 2.0 - JMCF for Jira Cloud

Our team is excited to announce the latest release of JMCF for Jira Cloud 2.0. This release includes the release of Scripted Fields! This release also includes additional functionality for the Time in Status custom field type, a Recalculate option in the My Custom Fields page, and other fixes for usability.

Scripted Fields!

Open

Scripted fields

This version of JMCF for Jira Cloud includes the release of Scripted Fields! Scripted fields are a new custom field that return values using JavaScript to calculate their output. Your JavaScript can access the values in other fields as well as the Jira APIs. Scripted fields can also be created with dependencies, triggering automatic recalculations if those fields are updated!

Scripted fields currently support a limited set of data types, including:

• Strings

• Datetimes

• Numbers

• Users - Returns an Atlassian account ID or a user object.

• Groups - Returns a group ID or a Group object.

• String collection - Returns a collection of string values.

• User collection - Returns a collection of user IDs or user objects.

• Group collection - Returns a collection of Group IDs or Group objects.

Other Enhancements

This release includes other updates and improvements:

• The Action menu in My Custom Fields page now includes a Recalculate option for individual fields.

• Time in Status custom fields will now update when an issue is opened for viewing, resulting in more accurate updates to those fields.

• Checking the All checkbox in the Create Custom Field screen selection when the list of screens is filtered will only select the visible screens.

• Custom field names can now include up to 255 characters.

Bug fixes

The following bugs are fixed in this release:

• Custom fields are not correctly updating when monitoring some fields

  • An issue sometimes occurred with JMCF custom fields not updating when configured to monitor another field using the field ID. This has been resolved.

  • The Transition Count custom field type was not updating its count correctly when it’s monitored field was continually updated. This has been fixed.

• Custom field configuration

  • For some custom field types, the “Field to watch” configuration field was not displaying its values correctly, resulting in an incomplete configuration. This has been resolved.

  • Occassionally, using the All button to select all screens would not work in the Create Custom Field Wizard, causing an error and preventing the custom field from being created. This has been fixed.