Insight 3.1 release notes
Performance
We are constantly trying to decrease the response times and enhance performance in general. In this release we have manage to reduce the time to re-index at startup by 70% compare to the previous version. Fetching objects in list view has been reduced by 50%. These figures is of course dependent on the server JIRA is installed on but this is great improvements in terms of performance.
Create References Directly from the attribute screen
If you don't find any suitable reference name, Insight will directly add one for you.
User type attribute now supports multi groups and is no more required.
When creating a new attribute of type "User", it was previously mandatory to specify a JIRA Group from where to fetch users. This is not mandatory anymore and you also may specify multiple JIRA groups.
Condition and Validator in transition
You can now use conditions or validators in JIRA workflow transitions. This could be really powerful in a lot of areas and use cases like:
- allow Change Request only if target server have enough license available
- allow Change Request only if target server is not in production
- allow holiday request only if user have enough remaining vacation days
- allow specific hardware request to be approved only if there are enough of hardware models available
- allow only specific request on servers that has a specific SLA level
Bug fixes
- JIRA Service Desk portal theme settings unavailable
- Tempo synchronization fails when contacts are non JIRA users
- LDAP fix when on scheduling synchronizations.
- IQL fixes
- SQL Server fix
- Escape characters missing/wrong in Insight selects
- Data consistancy error in object keys