This version includes bugfixes for Jira 9.5.0 and later, and patches an XSS vulnerability.

For the full list of changes, please refer to the full release notes.

This version includes bugfixes for Jira 9.5.0 and later, and patches an XSS vulnerability.

For the full list of changes, please refer to the full release notes.

This version includes updates to libraries which were affected by vulnerabilities.

This is a recommended update for all customers.

This version includes updates to libraries which were affected by vulnerabilities.

This is a recommended update for all customers.

For this release, we are thrilled to introduce the new logo for JMCF.

The following bug has been fixed:

• JMCF-437: Email addresses are now supported in single user calculated fields.

For this release, we are thrilled to introduce the new logo for JMCF.

The following bug has been fixed:

• JMCF-437: Email addresses are now supported in single user calculated fields.

JMCF 2.4.7 is now compatible with Jira 9.

This version contains the fixes for the following issues:

• XSS vulnerability in case of malicious project names patched.

• JMCF-396 - Time in status and Calculated Duration: follow the specified precision when the value is 0.

JMCF 2.4.7 is now compatible with Jira 9.

This version contains the fixes for the following issues:

• XSS vulnerability in case of malicious project names patched.

• JMCF-396 - Time in status and Calculated Duration: follow the specified precision when the value is 0.

This version includes a security improvement (CVE-2022-0540)

This is a recommended update for all customers.

This version includes a security improvement (CVE-2022-0540)

This is a recommended update for all customers.

This version contains the following bug fixes:

• JMCF-399 - Addressed Calculated Text field NPE issue on the simple search UI.
• JMCF-400 - Addressed "Exact Text searcher" searcher issue on the Issue navigator UI, when it was configured with 'Calculated (scripted) Text/Html Field'.

This version contains the following bug fixes:

• JMCF-399 - Addressed Calculated Text field NPE issue on the simple search UI.
• JMCF-400 - Addressed "Exact Text searcher" searcher issue on the Issue navigator UI, when it was configured with 'Calculated (scripted) Text/Html Field'.

This version contains the following bug fix:

• JMCF-398 - Fixed the error message on the Create screen when Status(es) is configured with 'Current Status' on 'Time in Status' field.

This version contains the following bug fix:

• JMCF-398 - Fixed the error message on the Create screen when Status(es) is configured with 'Current Status' on 'Time in Status' field.

This version contains the following bug fix:

• JMCF-379 - Time In Status field: cannot render on Create screens

This version contains the following bug fix:

• JMCF-379 - Time In Status field: cannot render on Create screens

The highlight of this version:

• When displaying a list of statuses, the 'Time in Status' field will sort statuses by their configured order as per on the Statuses page

For the bug fix, please refer to the full release notes

The highlight of this version:

• When displaying a list of statuses, the 'Time in Status' field will sort statuses by their configured order as per on the Statuses page

For the bug fix, please refer to the full release notes

This version contains the following bug fix:

• JMCF-374 - In Issue navigator, Calculated Text/HTML field shows error when the field is not associated with an issue type or project.

This version contains the following bug fix:

• JMCF-374 - In Issue navigator, Calculated Text/HTML field shows error when the field is not associated with an issue type or project.

JMCF 2.4.0 brings the following new features:

• New calculated Labels custom field type: You can now create calculated custom fields that return and display calculated labels, similar to custom labels fields.
• Jira Data Center Data Pipeline is now supported

Other improvements:

• Time in Status custom fields can now display the time spent in each status.
• You can now remove the collapse toggle on Calculated Wiki/Text/Html fields.

For more information and a list of bug fixes, see the full release notes.

JMCF 2.4.0 brings the following new features:

• New calculated Labels custom field type: You can now create calculated custom fields that return and display calculated labels, similar to custom labels fields.
• Jira Data Center Data Pipeline is now supported

Other improvements:

• Time in Status custom fields can now display the time spent in each status.
• You can now remove the collapse toggle on Calculated Wiki/Text/Html fields.

For more information and a list of bug fixes, see the full release notes.

This version contains the following bug fixes:

• JMCF-365 issue.getAsString doesn't return a string representation of the duration for Time In Status fields
• JMCF-345 JMCF's searchers are selected by default for matching standard custom fields

This version contains the following bug fixes:

• JMCF-365 issue.getAsString doesn't return a string representation of the duration for Time In Status fields
• JMCF-345 JMCF's searchers are selected by default for matching standard custom fields

This version contains a single bug fix:

• JMCF-363 JMCF 2.3.2 breaks sorting on fields that use [Time Tracking] Duration searcher and Number range searcher (statistics-compatible)

This version contains a single bug fix:

• JMCF-363 JMCF 2.3.2 breaks sorting on fields that use [Time Tracking] Duration searcher and Number range searcher (statistics-compatible)

You can now freely switch between Number Range Searcher (statistics-compatible), Duration searcher (24x7 durations), Time Tracking Duration searcher (work time durations) and Number range searcher search templates without a Full re-index.

Please note that if you are using the Number Range Searcher (statistics-compatible), Duration searcher (24x7 durations), or Time Tracking Duration searcher (work time durations) search template on at least one custom field, you will be asked to perform a Full re-index (not background) at your earliest convenience. While this full re-index is not mandatory, until you perform one, you will not be able to switch to/from these search templates without creating indexing errors.

For bug fixes, see the full release notes.

You can now freely switch between Number Range Searcher (statistics-compatible), Duration searcher (24x7 durations), Time Tracking Duration searcher (work time durations) and Number range searcher search templates without a Full re-index.

Please note that if you are using the Number Range Searcher (statistics-compatible), Duration searcher (24x7 durations), or Time Tracking Duration searcher (work time durations) search template on at least one custom field, you will be asked to perform a Full re-index (not background) at your earliest convenience. While this full re-index is not mandatory, until you perform one, you will not be able to switch to/from these search templates without creating indexing errors.

For bug fixes, see the full release notes.

This version contains the following changes:

Bug fixes

• [JMCF-337] - Calculated fields should have an html ID on transition/creation screens so they can be manipulated by JavaScript and ScriptRunner Behaviors
• [JMCF-339] - Transition Count Field throws exception when issue workflow history is invalid

This version contains the following changes:

Bug fixes

• [JMCF-337] - Calculated fields should have an html ID on transition/creation screens so they can be manipulated by JavaScript and ScriptRunner Behaviors
• [JMCF-339] - Transition Count Field throws exception when issue workflow history is invalid

JMCF 2.3.0 brings the following new features:

• Automatic re-indexing of related issues: you can now configure automatic re-indexing of issues related to any issue being modified. This will make calculated fields that depend on related issues work correctly in issue searching and dashboard.
• Calculated (Scripted) Date custom field type: similar to the Calculated Date/Time field type, but without the time part.

Other improvements:

• Better logging for easier debugging of calculated (scripted) fields
• Infinite recursions in calculated field formulas are now caught and logged
• It is now possible to access private components (services) of other apps from Groovy scripts (formulas)
• Calculated Wiki/Text/Html Fields now support collapsing long field values
• Duration calculated fields are now supported in the Confluence Jira macro
• Secure Fields are now accessed directly, bypassing security

For more information and a list of bug fixes, see the full release notes.

JMCF 2.3.0 brings the following new features:

• Automatic re-indexing of related issues: you can now configure automatic re-indexing of issues related to any issue being modified. This will make calculated fields that depend on related issues work correctly in issue searching and dashboard.
• Calculated (Scripted) Date custom field type: similar to the Calculated Date/Time field type, but without the time part.

Other improvements:

• Better logging for easier debugging of calculated (scripted) fields
• Infinite recursions in calculated field formulas are now caught and logged
• It is now possible to access private components (services) of other apps from Groovy scripts (formulas)
• Calculated Wiki/Text/Html Fields now support collapsing long field values
• Duration calculated fields are now supported in the Confluence Jira macro
• Secure Fields are now accessed directly, bypassing security

For more information and a list of bug fixes, see the full release notes.

New features:

• You can now create a Transition Callers field that will list all users who triggered one or more selected transition(s) on the issue.
• JMCF now supports the Configuration Manager app from Botron Software. This means that you will be able to use Configuration Manager to move JMCF custom fields from one Jira instance to another with only minimal effort (see the documentation for limitations).

Other improvements:

• Duration fields now support a precision setting (seconds, minutes, hours, days, weeks,...) that applies to both display and statistics
• You can now specify a custom Velocity template for List (column) view search results
• Time in Status fields: "most recent" now returns only the time spent since the last transition
• Improved display of Groovy scripts on configuration screens
• Calculated (scripted) Duration fields now support negative durations

For more details, see the full release notes.

New features:

• You can now create a Transition Callers field that will list all users who triggered one or more selected transition(s) on the issue.
• JMCF now supports the Configuration Manager app from Botron Software. This means that you will be able to use Configuration Manager to move JMCF custom fields from one Jira instance to another with only minimal effort (see the documentation for limitations).

Other improvements:

• Duration fields now support a precision setting (seconds, minutes, hours, days, weeks,...) that applies to both display and statistics
• You can now specify a custom Velocity template for List (column) view search results
• Time in Status fields: "most recent" now returns only the time spent since the last transition
• Improved display of Groovy scripts on configuration screens
• Calculated (scripted) Duration fields now support negative durations

For more details, see the full release notes.

This version provides the following enhancement and bug fixes:

Enhancement:

• The Exact Text Searcher (stats-compatible) now supports displaying html text in statistic gadgets

Bug fixes:

• [JMCF-311] - Cannot load FastStringService exception when using Groovy's JsonSlurper
• [JMCF-316] - Calculated date/time field and Last Field Change Date/Time field don't take the user's time zone to format the value

This version provides the following enhancement and bug fixes:

Enhancement:

• The Exact Text Searcher (stats-compatible) now supports displaying html text in statistic gadgets

Bug fixes:

• [JMCF-311] - Cannot load FastStringService exception when using Groovy's JsonSlurper
• [JMCF-316] - Calculated date/time field and Last Field Change Date/Time field don't take the user's time zone to format the value

This version fixes one bug:

• [JMCF-311] - Cannot load FastStringService exception when using groovy.json.JsonSlurper

This version fixes one bug:

• [JMCF-311] - Cannot load FastStringService exception when using groovy.json.JsonSlurper

This version brings the following changes:

Improvements:

• Wiki rendering is automatically configured for Calculated (scripted) Wiki Text Fields upon saving the formula.
• When testing a script, the issue against which it is tested is now displayed in the results.

Bug Fixes:

• [JMCF-306] - Groovy tester now highlights the correct line where the exception occurred
• [JMCF-308] - The Add button of the Transitions configuration page could sometimes remain grayed out after entering a transition name or ID

This version brings the following changes:

Improvements:

• Wiki rendering is automatically configured for Calculated (scripted) Wiki Text Fields upon saving the formula.
• When testing a script, the issue against which it is tested is now displayed in the results.

Bug Fixes:

• [JMCF-306] - Groovy tester now highlights the correct line where the exception occurred
• [JMCF-308] - The Add button of the Transitions configuration page could sometimes remain grayed out after entering a transition name or ID

This version fixes a regression introduced by the recent upgrade to Groovy engine version 2.5, which prevented date calculations from working.

This is a recommended update for all customers.

This version fixes a regression introduced by the recent upgrade to Groovy engine version 2.5, which prevented date calculations from working.

This is a recommended update for all customers.

This version fixes a regression introduced by the recent upgrade to Groovy engine version 2.5, which prevented date calculations from working.

This is a recommended update for all customers.

This version fixes a regression introduced by the recent upgrade to Groovy engine version 2.5, which prevented date calculations from working.

This is a recommended update for all customers.

This version fixes an excessive cache memory consumption issue, especially visible on Jira Data Center (JMCF-303). It also upgrades the Groovy engine to version 2.5.

This is a recommended update for all customers.

This version fixes an excessive cache memory consumption issue, especially visible on Jira Data Center (JMCF-303). It also upgrades the Groovy engine to version 2.5.

This is a recommended update for all customers.

JMCF 2.1.0 is an update to JMCF 2.0. For more info about JMCF 2, visit this page.

JIRA 8 COMPATIBILITY

JMCF 2.1.0 is fully compatible with Jira Software/Core 8, as well as with Jira Service Desk 4.0. JMCF 2.1.0 is also backward compatible with Jira 7.0.11 and above.

See the full release notes for details about other new features and bug fixes.

LIMITED TIME OFFER! Get 30% off on JMCF if you upgrade on or before March 31st.

JMCF 2.0.1 is a minor update to JMCF 2.0. For more info, see the full release notes.

JMCF 2.0 is a complete rewrite of our previous version and it now offers twice as many calculated field types, better usability, and more powerful - yet easy - scripting.

Highlights include:

• Much easier configuration through the standard custom field configuration page
• Powerful scripting through the use of the same Groovy language as our leading JMWE for Jira Server app, with the same simplified Groovy API to help you write sophisticated formulas in no time. It offers the same powerful editor with syntax highlighting and on-the-fly syntax checking, inline help system, and integrated script tester to get things done faster and more accurately.
• Nine new custom field types
• And a completely rewritten documentation

For more information, read the full release notes.

LIMITED TIME OFFER! Get 30% off on JMCF if you upgrade on or before March 31st.

We're excited to announce the release of JMCF 2.0. It is a complete rewrite of our previous version and it now offers twice as many calculated field types, better usability, and more powerful - yet easy - scripting.

Highlights include:

• Much easier configuration through the standard custom field configuration page
• Powerful scripting through the use of the same Groovy language as our leading JMWE for Jira Server app, with the same simplified Groovy API to help you write sophisticated formulas in no time. It offers the same powerful editor with syntax highlighting and on-the-fly syntax checking, the same inline help system, and the same integrated script tester to get things done faster and more accurately.
• Easier troubleshooting through direct access to errors on the issue view page
• Eight new custom field types
• And a completely rewritten documentation

For more information, read the full release notes.

New Feature:

• [JMCF-205] - Last Field Value Change Author Field

Improvement:

• [JMCF-207] - Make JMCF date/time field format configurable for both display and list views

Bug fixes:

• [JMCF-197] - Last Field Change Date breaks /rest/api/2/issue/<issuekey>/editmeta
• [JMCF-198] - JMCF incorrectly re-indexes stale subtasks
• [JMCF-206] - Calculated fields should return null when not applicable to current issue

Bug fixes:

• [JMCF-195] - DB errors occurring after latest update to 1.6.3 on Oracle 10g
• [JMCF-196] - issue.get("comment") is broken

This release brings compatibility with Jira 7.

Bug fixes:

• [JMCF-195] - DB errors occurring after latest update to 1.6.3 on Oracle 10g
• [JMCF-196] - issue.get("comment") is broken
• [JMCF-197] - Last Field Change Date breaks /rest/api/2/issue/<issuekey>/editmeta
• [JMCF-198] - JMCF incorrectly re-indexes stale subtasks

Bug fix:

• [JMCF-193] - Transition Date/Time field causes exception with PostgreSQL 8.3+

Bug fix:

• [JMCF-180] - Transition Calculated fields don't support switching from one workflow to another

Improvement:

• [JMCF-160] - issue.get() should support identifying custom fields by their nam

Improvements:

• [JMCF-150] - Calculated fields' formula error should be more explicit
• [JMCF-166] - Make custom Field errors more explicit
• [JMCF-173] - Make the BeanShell interpreter pool configurable

Bug fix:

• [JMCF-168] - Transition Date/Time and Caller Fields sometimes leak SQL ResultSets

Improvement:

• [JMCF-150] - Calculated fields' formula error should be more explicit

New Feature:

• [JMCF-144] - Add a "Last Field Value Change Date/Time Field" calculated field

Bug fixes:

• [JMCF-148] - @@Format doesn't work for Calculated Date Fields in Jira 6+
• [JMCF-151] - Calculated Fields don't work with the Issue Links field in Jira 6.3
• [JMCF-154] - Some packages are not available in Calculated Field Scripts

Bug Fix:

• [JMCF-139] - Enabling Jira Misc Custom Fields makes updates of all other plugins unresponsive on Jira < 6.3

New Feature:

• [JMCF-138] - Transition Count Field

• [JMCF-132] - Transition date/caller fields not filled if user details not available

Bug fixes:

• [JMCF-111] - Transition caller fields don't work in REST api
• [JMCF-113] - Calculated custom fields cannot use some Java packages reliably
• [JMCF-130] - Query on Transition Caller Field reports empty results for users with uppercase letter in username

New Feature:

• [JMCF-126] - Jira Data Center compatibility

Bug

• [JMCF-91] - Transition history fields don't work on Oracle databases

Bug

• [JMCF-72] - Transition Date/Time Field Always empty
• [JMCF-77] - Jira 6: calculated number field formatter cannot return html code
• [JMCF-79] - Transition Date/Time Field not working on MS SQL Server backend

New Feature

• [JMCF-82] - Add a new Exact Text Searcher to the Calculated Text Field custom field type

Bug

• [JMCF-71] - Calculated Number Field formatting does not apply locale

Improvement

• [JMCF-60] - Improve indexing performance when using calculated fields

New Feature

• [JMCF-62] - Calculated String and Calculated Date Field types

Bug

• [JMCF-66] - Enabling Misc custom fields causes stack trace and errors.

Bug

• [JMCF-58] - Logging is broken under Jira 5.2

New Feature

• [JMCF-65] - Jira 6 compatibility

Bug

• [JMCF-44] - Oracle error - ORA-00932: inconsistent datatypes: expected - got CLOB

Improvement

• [JMCF-60] - Improve indexing performance when using calculated fields

Bug

• [JMCF-44] - Oracle error - ORA-00932: inconsistent datatypes: expected - got CLOB
• [JMCF-58] - Logging is broken under Jira 5.2

Improvement

• [JMCF-39] - Expose com.atlassian.jira.issue.Issue instance as context variable

New Feature

• [JMCF-20] - Allow date and user logging for targetstatus next to transition
• [JMCF-50] - Allow to get first or last date of a transition to a target status

Support Request

• [JMCF-51] - Is it possible to have the Issue Navigator show the actual date of the Transition Date

Bug

• [JMCF-44] - Oracle error - ORA-00932: inconsistent datatypes: expected - got CLOB

Improvement

• [JMCF-39] - Expose com.atlassian.jira.issue.Issue instance as context variable

New Feature

• [JMCF-20] - Allow date and user logging for targetstatus next to transition
• [JMCF-50] - Allow to get first or last date of a transition to a target status

Support Request

• [JMCF-49] - NullPointerException when using customUserPropertyAsList function in filter
• [JMCF-51] - Is it possible to have the Issue Navigator show the actual date of the Transition Date

• Jira 5.1 compatibility
• [JMCF-27] - Field "aggregatetimeestimate" is not available as documented
• [JMCF-33] - Parent Status Field search results does not update until reindex

• [JMCF-24] - Cannot get issue links in Calculated custom field
• [JMCF-27] - Field "aggregatetimeestimate" is not available as documented
• [JMCF-33] - Parent Status Field search results does not update until reindex

Jira 5 compatibility.

Bugs:

• [ JMCF-19] - Transition Search custom fields don't find transitions across workflow changes
• [ JMCF-21] - Transition User calculated field is not properly indexed

Improvement:

• [ JMCF-18] - Enable custom formatting for Calculated number field values

[ JMCF-15] - Add a Parent Status field type

• [ JMCF-13] - Transition search fields are broken on MySQL

• [ JMCF-14] - Transition search fields should respect standard people and datetime formatting and display section

• [ JMCF-7] - NullPointerException for Calculated Number Field with empty description

• [ JMCF-11] - Create transition search calculated fields

• [ JMCF-10] - How to set Calculated Number Field to null without NPE

[ JMCF-3] - Incompatibility with Jira 4.3