First, on behalf of Innovalog, I would like to take this opportunity to thank all our customers for their business. This patronage truly matters to us, especially in these turbulent times. We strive to meet and exceed expectations whenever our customers need help, have a question, or reach out to our support team, and we are always committed to doing our best.
At Innovalog, we never increase our prices without first giving you valuable new functionality to automate more of your Jira processes. In the past 12-18 months, we have invested in a significant amount of new features and improvements, and we hope you find them helpful. This year, we have decided to make all pricing changes in one shot, on September 16th, 2020, as we have postponed some pricing changes from Spring to help organizations stabilize their business during this difficult time.
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).
Build a"low effort - high impact" Jira story report with the help of JMCF and Excel
All agile teams know the value of adaptive planning and quick response to change. While there are many tools and strategies that help you evaluate and prioritize - and reprioritize - your work, one you can always count on is "impact vs. effort."