| Expand | ||
|---|---|---|
| ||
🎉Support added for including 'Account' custom field from Tempo timesheets plugin 🎉Custom field variables in sequential templates back to the previous syntax Couple of releases ago, we had unknowingly changed the syntax of custom field variables in sequential templates to
🎉Conditional triggers based on version names are here 🤘 In case of automated triggers, rules are executed for all versions. Not anymore. Now you can configure a regular expression to match with the version name so that the rule is executed only for specific versions. For example, V 1.0 major release will trigger the rule but V 1.1 patch release not.
🐞Non-English characters supported in the POST action |
...
| Expand | ||
|---|---|---|
| ||
🐞Custom fields in sequential layouts were broken, fixed Inadvertently, the custom field formats that we use in sequential layouts had an unnecessary underscore. This caused the existing templates to break. We have now addressed the root cause. |
...
| Expand | ||
|---|---|---|
| ||
🎉✏️. More appropriate & intuitive icon introduced for Edit 🐞Templates with images from local Jira servers weren't saving To protect cloud application from SSRF attacks, we’ve blocked saving images 🖼️ as locally hosted URLs. This had an impact on server, now resolved. 🐞Group by fix version formatting version name bug 🧬 While grouping by fix version, the version names in release notes were being 🥪 sandwiched between double quotes. Fixed 🐞URL custom fields were not rendered as links If you were using URL type of custom fields and pulled them into release notes, they were not being rendered as links. Resolved 🔗 |
...