Feature Release 2.1 - JMCF for Jira Cloud

Our team is thrilled to announce the latest release of JMCF for Jira Cloud 2.1. This release includes several updates to JMCF Cloud, including Scheduled Recalculations, improved dependency detection and return data type checking for scripted fields, and various UI updates for clarity and performance.

Administration

Scheduled Calculations

Custom fields can now be scheduled to (re)calculate on demand! For scenarios where custom fields take a long time to recalculate or when updated data is critical, you can now schedule individual custom fields to recalculate on a set interval. See Scheduled recalculations for more details.

Enable and Disable Custom Fields

Custom fields can now be enabled or disabled from the My Custom Fields page. Disabling a custom field will remove it from any issue screens and remove any scheduled calculations. <answers to questions go here>

Custom Fields

Scripted Fields autodetect dependent fields and properties

When entering a script for a Scripted field, JMCF for Jira Cloud will now autodetect any issue fields or issue properties that are accessed in the script and will add them to the list of dependencies. Dependencies enable triggering an automatic recalculation of the scripted field when its underlying data is updated. See Scripted Field Dependencies section for more details.

Improved return data validation for Scripted Fields

The Scripted fields code editor now include additional feedback for the expected output data type of your script, and whether or not that type matches the configured data type for your field (e.g. string, datetime, number, etc.).

‘Status Entered’ fields now supports multiple status values

The Status Entered Time and Status Entered by User custom field types now support selecting multiple status values to be monitored. When selecting multiple status values, a change in status to any of the selected values will trigger an update to the custom field.

Improved JQL support for ‘Time in Status’ field

Querying Time in Status custom fields has been enhanced to support a variety of representations of time (e.g. 2days3hours42minutes17seconds or 2d3h42m17s), as opposed to searching only by seconds. This includes searching by number of days (days or d), hours (hours or h), minutes (minutes or m), as well as by seconds (seconds or s).

Other Enhancements

Custom domain support

JMCF for Jira Cloud is now supported when running Jira on custom domains.

UI fixes

Several UI components have been update for consistency, clarity, and performance.

Bug fixes

The following bugs are fixed in this release:

• Parent status custom fields displaying on all issues

  • The ‘Parent status’ custom field type was incorrectly displaying on all issues instead of only on child issues. This has been resolved.

• ‘Field to watch’ option not required

  • The ‘Field to watch’ configuration is required for some custom fields, but in some scenarios it was possible to save the custom field configuration without selecting a field. This has been fixed.

• Create Custom Field Wizard accidentally closing

  • Clicking outside of the Create Custom Field Wizard dialog was incorrectly closing the wizard and resulting in loss of configurations. This has been fixed.

• Column sorting on Error logs page

  • Some column sorting options on the Error logs page were not working correctly. This has been resolved.

• Search box unavailable when using Create Custom Field Wizard

  • The Search box at the top of the

• Incorrect sorting for edited fields

  • The My Custom Fields page was not displaying recently edited fields correctly. Newly edited fields will now display at the top of the page, unless other sorting has been applied.

• ‘Acknowledge all errors’ and ‘Delete all errors' buttons incorrectly displaying

  • These two buttons were incorrectly displaying on the Error logs page when there were no errors to acknowledge or delete. They will not longer display in this scenario.

• Editing a custom field fails after deleting default Context

  • After deleting the context for a custom field it was not possible to then edit the custom field through the My Custom Fields page. This has been resolved.

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!

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.