In this release
Use Russian or most UTF-8 characters in property names, values and in the search.
Release 2.4.1
This is rather a technical release, to check everything works well with some big underlying change:
- We are now using Javascript/ES6. It shouldn't be visible from the user's point of view but, in case of issue, you can downgrade back to 2.3.3.
- We support UTF-8 in property names and values! (long-awaited feature) We also support numbers, for example "baseline = 1" is now legal.
- We've removed the "Email our support from within the app" feature, for GDPR compliance.
- We've disabled jobs when Confluence was in read-only mode.
Release 2.4.2 – Not published yet
We first want to ensure the deployment of 2.4.1 works well for everyone. Then we'll publish 2.4.2.
Our change: We index properties differently.
- Before: We used to let the user search on the HTML of the properties,
- After: We've split the column between display and search, so what is displayed is the HTML, but what can be searched is the textual content of a value.
Example: If a property contained a status, the HTML would be something like <span class="status-success">OK</span>, and the search query would be @Property = '<span class="status-success">OK</span>'
| Stored data for display | Stored data for search | Displayed as | Search query | Comments | |
|---|---|---|---|---|---|
| Before | <span class="status-success">OK</span> | (None, it didn't exist) | OK | @Property = '<span class="status-success">OK</span>' | The search was ugly. |
| After | <span class="status-success">OK</span> | "OK" | OK | @Property = 'OK' | Awesome. |
I hope you understand that this is a major improvement, and will be satisfied with the implementation.