← Back to Release Notes

Open

Feature Release - JMCF for Jira Cloud 7.0

Release date: June 30, 2025

Our team is thrilled to announce the latest release of JMCF for Jira Cloud 7.0. This release includes the new Time in Status Table custom field, scripted duration fields, updates to field formatters, and various bug fixes. Additionally, Data Residency support has been implemented.

Open

Run on Atlassian

Lastly, JMCF for Jira Cloud now Runs on Atlassian! Forge apps that are certified as Runs on Atlassian meet advanced standards for security and data management, including data residency compliance and hosting of the app within Atlassian systems.

Contents

Contents
1 Feature Release - JMCF for Jira Cloud 7.0 1.1 Custom Fields 1.1.1 Time in Status Table custom field 1.1.2 Scripted duration custom field 1.1.3 Duration field formatters 1.2 Platform 1.2.1 Data residency support 1.3 Bug Fixes

Custom Fields

Time in Status Table custom field

A brand new custom field type has been added to JMCF for Jira Cloud - the Time in Status Table field! This field can be used to monitor total time spent in two or more statuses, and creates a table of values displaying cumulative times for each status as well as total time for all statuses. See Time in Status Table for more information!

Scripted duration custom field

Scripted custom fields have been expanded to include a duration type. This scripted field type returns a duration value in seconds and can be formatted to display its values in various formats. See Scripted Fields for more information.

Duration field formatters

Duration fields - Time in Status, Time in Status Table, and Scripted Duration - now include Formatter options. Display options include how to format the duration value, rounding, and precision settings. See Formatters for more information.

Platform

Data residency support

JMCF for Jira Cloud now supports Atlassian Data Residency. Long-term data in JMCF can now be limited to specific geographical regions. See Data Residency and JMCF for more information.

Bug Fixes

• 'Test with issue' error messages are unclear - The Test with issue feature does not always return useful error messages when testing a new custom field configuration. Error messages have been improved across all custom field types.

• Custom fields cannot be enabled when created through Jira native UI - When a JMCF custom field is created through the native Jira custom field process, that custom field cannot be enabled through the My Custom Fields administration page. This has been resolved.

• ‘Test with issue’ not visible when editing scripted fields - When editing a JMCF scripted field through the native UI (Configure custom field → Custom field config) the results are not visible when using the Test with issue feature. This has been resolved.

• Associating screens with new custom fields is inconsistent when using the ‘All Screens’ option - When creating a new custom field and using the All Screens option, the resulting custom field will occasionally miss association with some screens. This is due to rate limiting from Atlassian, but has been resolved in the method JMCF uses for fetching screens and associating new custom fields.

• Sorting broken for some columns in administration pages - The ‘Description’ column on the My Custom Fields administration page and the ‘Context’ column on the Calculations administration page are not sorting correctly. This has been resolved.

• Formatters preview for date and datetime fields do not match configuration - The preview displayed in the Formatters configuration screen for the Time Zone setting does not match the configuration selected (e.g. when selecting UTC, the preview displays GMT). This has been resolved.