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.
JMCF 2.0 is a collection of calculated field types that enable the creation of additional fields to display information based on computed values. You can tailor them to your organization’s needs - deploy more useful screens, enable better search and filters for users, and build more powerful dashboards for managers.
For example, you can:
- calculate values based on other fields within the same issue
- display aggregated values of related issues
- display related Jira data, such as the release date of the issue’s Fix version
- and so much more.
Since JMCF 2.0 is a commercial release, we now provide the same level of support as with our other products.
What’s new in JMCF 2.0:
Forget cumbersome configuration embedded as HTML comments in field descriptions - calculated fields are now configured the same way as standard Jira custom fields, right on the "Configure" page:
JMCF 2.0 now uses 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.
If you are a Jira administrator, any error related to a calculated custom field will be displayed right on the Issue View screen, making it very easy to troubleshoot:
New Calculated Field Types
We have added the following brand new calculated field types to help you address even more of your business needs:
Calculated (Scripted) Multi-select custom field type
A Calculated Multi-select custom field type represents a collection of Options and is displayed as a String representing the option values. It is a read-only field. You will need to configure options to this field just like any Jira Standard custom field of Multi-select list/Checkboxes type.
Calculated (Scripted) Single-select custom field type
A Calculated Single-select custom field type represents an Option and is displayed as a String representing an Option value. It is a read-only field. You will need to configure options to this field just like any Jira Standard custom field of Single select list/Radio buttons type.
Status Entered by User custom field type
A Status entered by user custom field type represents the user who last (or first) moved the issue to the specified status and is displayed as a String representing the user display name. It is a read-only field.
Status Entered on Date/Time custom field type
A Status entered on Date/Time custom field type represents the date+time the issue has been last (or first) moved to the specified status and is displayed as date+time. It is a read-only field.
Time in status custom field type
A Time in status custom field type represents a duration and is displayed either as a duration String or as a number in a Long format representing the number of seconds. It is a read-only field.
Click here to see all calculated fields with their definitions, or explore some use case examples here.
Enhanced Calculated Field Types
Transition Caller Field, Transition Date/Time Field, and Transition Count Field now all support multiple transitions, by name or by ID, as well as optionally specifying workflows to which they will apply.
Also, as mentioned above, all script-based calculated fields now use the much more powerful Groovy language.
Powerful Search and Dashboard Enablement
Every JMCF calculated field supports multiple search templates that make it easy to search for issues based on that field. They even support dashboard statistics gadgets! As an added value, JMCF search templates can also be used with non-JMCF custom fields. For example, you can use JMCF's "Date Time Searcher (Statistics-compatible by month)" to create statistics by months on a standard date/time picker field.
Completely Rewritten Documentation
Our new, comprehensive documentation provides an in-depth list of configuration details, many examples and use cases, how-tos, and a code snippet library. You can access the documentation here.