Page History
...
- Added optional parameter "Update issue immediately after field writing" to the following post functions:
- Copy parsed text to a field
- Format field value
- Mathematical and date-time expression calculator
- Parse field for extracting data
- Read a project property
- Read field from issues returned by JQL query or issue list
- Read fields from linked issues or sub-tasks
- Read user property
- Regular expression renderer
- Set a field as a function of other fields
- Write field on issues returned by JQL query or issue list
- Write field on linked issues or sub-tasks
In version 2.3.3 issues stopped to be immediately updated after each field writing. This modification of the historical behavior of JWT has caused not few problems in some workflows configured with previous versions of JWT. In this new version of JWT (2.3.4) we are adding a checkbox parameter for optionally updating the issue after a field writing. This parameter is by default checked in old post-function configurations, thus we keep the historical behavior of JWT avoiding back-compatibility issues.
Bug fixes
- Unary minus operator caused NPE when applied on numeric expressions returning
null. - Optional parameter "Don't overwrite" wasn't working in post functions Read field from issues returned by JQL query or issue list and Read fields from linked issues or sub-tasks.
- Post function Send an email didn't manage correctly attachments using Cyrillic characters in the file name.
- Functions replaceFirst() and replaceAll() caused NPE when applied on null arguments arguments.
