| Expand | ||
|---|---|---|
| ||
🎉Now publish a Confluence page with Jira issue filter macro ARN You can now use Jira issue filter macro right within the ARN template. That means, if you need the release notes to be dynamic - just use this macro
🎉Cross project release calendar is here 🥳 As many of you requested, we have brought on cross project release calendar to ARN. Here is the help article to get you started. Check out the screenshot below.
🐞Confluence space key in small caps caused update action to fail 🙄 If your Confluence space key was in small letters, that caused the update action from ARN to fail with a cryptic error message. This is now fixed 🎉
|
...
| Expand | ||
|---|---|---|
| ||
🎉Support for German, French & Russian languages is here 🏁 We are excited to unveil support for German 🇩🇪, French 🇫🇷 & Russian 🇷🇺 languages. We are gradually expanding this list. If you are looking for a specific language, reach out to our support. 🎉It is now easier than ever to keep an eye on ARN's integrations 🧐 We came across lot of errors in rule execution logs for simple reasons such as modified credentials, missing configurations & so on. Now with ‘Integration status’, anyone with access to ARN screen can spot Green/Amber/Red indicator and see detailed connection status within the Help tab. Check out the sample below.
🐞Version names in special characters caused JQL validation errors 🤓 If you used the 2.7 variable within the JQL section of ARN templates & tried to use a version which had special characters in it, validation bombed 💥. This is now fixed. |
...
| 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 |
...