You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
JMCF v. 2.3.0 for Jira Server and Data Center is here, and it brings the following new features:
When displaying an issue, the value of all its Calculated (Scripted) fields is re-computed on-the-fly. Therefore, the value of any Calculated field will always be up-to-date. But when searching for issues, Jira uses the Jira index, which stores the value of all standard and custom fields and is only updated when an issue is modified (or the index is re-built).
So, in cases when the script accesses data from related issues -- sub-tasks, linked issues, stories of an Epic, etc. -- the issue will not be re-indexed if one of the related issues is modified, which can lead to the index becoming obsolete for that issue, thus making search results and data in dashboards incorrect.
To work around this Jira limitation, JMCF can now force Jira to re-index related issues when an issue is modified. However, this will increase the Jira workload, and it should, be used with caution, and only on projects and/or issue types where it is needed, and only for the right issue relationships.
The Calculated (Scripted) Date custom field type is similar to the Calculated Date/Time field type, but without the time part - to be used to display and search by date without time. This makes it easier for searching and creating statistics. Plus, this will handle local time zones much better - it will show the right date irrespective of the time zone (just like Jira Standard field Due date).