App was not working after upgrading the version to 2.9

App was not working after upgrading the version to 2.9

• We bring to you the ability to append/prepend release notes to an existing Confluence page, directly from ARN.
• confluenceURL variable is now supported. Simply utilise the Confluence URL in other templates and it will share where the ARN published your release notes.
• Ability to refresh the logs with a click of a button
• Other minor enhancements and bug fixes

• We bring to you the ability to append/prepend release notes to an existing Confluence page, directly from ARN.
• confluenceURL variable is now supported. Simply utilise the Confluence URL in other templates and it will share where the ARN published your release notes.
• Ability to refresh the logs with a click of a button
• Other minor enhancements and bug fixes

• As many of you requested, 1st version of cross project release calendar is now live. We will be soon enhancing this with cross project templates & rules for release notes generation.
• Confluence template builder within ARN now supports Jira issue filter macro.
• Bug that prevented templates from being deleted if the rules they are used in are already deleted is now fixed.

• As many of you requested, 1st version of cross project release calendar is now live. We will be soon enhancing this with cross project templates & rules for release notes generation.
• Confluence template builder within ARN now supports Jira issue filter macro.
• Bug that prevented templates from being deleted if the rules they are used in are already deleted is now fixed.
• Jira 8.16 compatibility

Version 2.7 had introduced a bug with the 'Integration status' feature. If you've upgraded to that version, then you will have to update your credentials for all integrations e.g. Confluence & JSD. If you are directly updating to this version, you don't have to do anything.

Version 2.7 had introduced a bug with the 'Integration status' feature. If you've upgraded to that version, then you will have to update your credentials for all integrations e.g. Confluence & JSD. If you are directly updating to this version, you don't have to do anything.

• Support for German, French & Russian languages is here 🏁
• Version names in special characters caused JQL validation errors 🤓, fixed
• It is now easier than ever to keep an eye on ARN's integrations 🧐

Check out the release notes on Confluence or on the release page

• Support for German, French & Russian languages is here
• Version names in special characters caused JQL validation errors , fixed
• It is now easier than ever to keep an eye on ARN's integrations 🧐

Check out the release notes on Confluence or on the release page

• 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.

• 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{epic_link_(customfield_10000)}. Now it is back to what it was before {epic_link(customfield_10000)}. We’ve updated all the templates for you, you don’t need to do anything.

• Non-English characters supported in the POST action

• Support added for including 'Account' custom field from Tempo timesheets plugin

• 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.

• 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{epic_link_(customfield_10000)}. Now it is back to what it was before {epic_link(customfield_10000)}. We’ve updated all the templates for you, you don’t need to do anything.

• Non-English characters supported in the POST action

• Support added for including 'Account' custom field from Tempo timesheets plugin

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.

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

• Data center migration tasks improvement
• More appropriate edit icon used across the app
• Group by fix version was adding double quotes to the version names, fixed
• Templates couldn't be saved from locally hosted Jira servers, resolved
• Custom field of type URL wasn't rendering as a link, addressed

• Data center migration tasks improvement
• More appropriate edit icon used across the app
• Group by fix version was adding double quotes to the version names, fixed
• Templates couldn't be saved from locally hosted Jira servers, resolved
• Custom field of type URL wasn't rendering as a link, addresse

• Extend "Scheduled before N days of release" up to 50 days
• Enable Confluence action to update existing page (prepend & append coming soon)
• Show settings icon in the field listing page on JQL section pop up
• Support JSD fields - customer satisfaction score, customer satisfaction date
• Other bug fixes

• Extend "Scheduled before N days of release" up to 50 days
• Enable Confluence action to update existing page (prepend & append coming soon)
• Show settings icon in the field listing page on JQL section pop up
• Support JSD fields - customer satisfaction score, customer satisfaction date
• Other bug fixe

Rule executions were being blocked due to a faulty line of code, now fixed.

Rule executions were being blocked due to a faulty line of code, now fixed.

• It is now possible to configure header & footer in PDF templates of ARN
• Stats can now be generated as links
• Jira 8.13 compatibility
• Other minor bug fixes

• It is now possible to configure header & footer in PDF templates of ARN
• Stats can now be generated as links
• Jira 8.13 compatibility
• Other minor bug fixes

• It is now possible to clone JQL sections
• Custom field id is displayed in field selector (JQL section pop-up) so that it is easy to spot custom fields vs default fields in Jira
• Page property macro now supports ability to add stats
• Now it is possible to clone a global template
• PDF release notes file names can be easily configured with help of variable

• It is now possible to clone JQL sections
• Custom field id is displayed in field selector (JQL section pop-up) so that it is easy to spot custom fields vs default fields in Jira
• Page property macro now supports ability to add stats
• Now it is possible to clone a global template
• PDF release notes file names can be easily configured with help of variabl

• Support hyperlinking from visual template builder (Cloud & Server)

• Calendar tab

• Posting Confluence Page to different Confluence instances

• Support hyperlinking from visual template builder (Cloud & Server)

• Calendar tab

• Posting Confluence Page to different Confluence instances

• ARN is now compatible with Jira 8.11
• Help tab is now available from within the app for quickly accessing all the ARN links.
• Minor bug fixes

• ARN is now compatible with Jira 8.11
• Help tab is now available from within the app for quickly accessing all the ARN links.
• Minor bug fixes

• Template that included Confluence macro with a line-break was failing on Confluence's side. Now fixed.

• Template that included Confluence macro with a line-break was failing on Confluence’s side. Now fixed.

• In the recent release, the empty check flag wasn't working & release notes were generated even when no issues were returned by any of the JQL sections. That is now solved.

• In the recent release, the empty check flag wasn't working & release notes were generated even when no issues were returned by any of the JQL sections. That is now solved.

• 'Hide section' when no results returned by the JQL checkbox wasn't working and always showed message 'No issues' irrespective of the configuration when 0 issues were returned by the JQL.

• 'Hide section' when no results returned by the JQL checkbox wasn't working and always showed message 'No issues' irrespective of the configuration when 0 issues were returned by the JQL.

Server & DC version of the app is now migrated to a new architecture that will help us speed up our new feature development. In addition to the look & feel enhancements, this update comes with support for a few more Confluence macros such as - Properties & Status.

There are changes in the database structure as well. If you are upgrading from a very old version of ARN, there could be problems. Do reach out to us if you come across any.

Also, the app is now compatible with Jira version 8.9

Server & DC version of the app is now migrated to a new architecture that will help us speed up our new feature development. In addition to the look & feel enhancements, this update comes with support for a few more Confluence macros such as - Properties & Status.

There are changes in the database structure as well. If you are upgrading from a very old version of ARN, there could be problems. Do reach out to us if you come across any.

Also, the app is now compatible with Jira version 8.9

Server & DC version of the app is now migrated to a new architecture that will help us speed up our new feature development. In addition to the look & feel enhancements, this update comes with support for a few more Confluence macros such as - Properties & Status.

There are changes in the database structure as well. If you are upgrading from a very old version of ARN, there could be problems. Do reach out to us if you come across any.

Also, the app is now compatible with Jira version 8.9

• View source option was disabled when the release notes were previewed inside the editor, that is now fixed.
• Apostrophe in JQL was causing the query to fail, addressed.
• Jira 8.7 compatibility

• View source option was disabled when the release notes were previewed inside the editor, that is now fixed.
• Apostrophe in JQL was causing the query to fail, addressed.
• Jira 8.7 compatibility

• New trigger introduced to schedule rules on a pre-defined frequency
• New configuration added to control max issues returned by JQL
• Jira 8.6 compatibility

• New trigger introduced to schedule rules on a pre-defined frequency
• New configuration added to control max issues returned by JQL
• Jira 8.6 compatibility

It is now possible to add custom styling for release notes that are generated via tabular format templates. Read the relevant documentation here.

It is now possible to add custom styling for release notes that are generated via tabular format templates. Read the relevant documentation here.

• In JSD type of project when "Customer Request Type" field is used as Group by field it was not showing correct value.
• When "Issue Type" or "Priority" field is used as Group By field the option to show it as text was missing - actually it was random earlier due JS error and was not working.
• pdf lib version is bumped to latest available version.

• In JSD type of project when "Customer Request Type" field is used as Group by field it was not showing correct value.
• When "Issue Type" or "Priority" field is used as Group By field the option to show it as text was missing - actually it was random earlier due JS error and was not working.
• pdf lib version is bumped to latest available version.

• Jira 8.4 compatibility
• Bug fix - customer request type field was returning unreadable object, that is now fixed

• Jira 8.4 compatibility

• Bug fix - Customer request type field on JSD tickets was returning unreadable values, that is now fixed

Release notes generation was causing problems when the issue summary contained < or > special characters, that is now fixed.

There was a problem in release notes generation when any of the issue summary had special characters > or < - that is now fixed.

• There was a bug related to Rules & templates sorting that happened on only one known instance. It has been addressed.

• There was a single report about rules & templates not being rendered on screen. We have fixed this so that there is no scope for such rendering error to happen.

Jira 8.3 compatibility & minor bug fixes

Jira 8.3 compatibility & minor bug fixes

• Jira data center compatibility

Data center compatibility

• Additional logging for POST action troubleshooting
• changed the cdf4j and winp lib version to latest

This is a compatibility release for Jira 8.2

ARN is now compatible with Jira version 8.1

It is now possible to use 'Stats' within release notes templates. Read more about stats here

• Jira 8 Compatibility
• Bug fix related to release notes POST action

• Ability to add current date in templates
• Ability to POST the release notes data to a pre-defined url
• Ability to view project key for global templates
• Bug fixes related to special characters (confluence templates)

• PDF generation issue further corrected

• There was a problem in detecting the chrome library used for pdf generation, that is now address.
• Minor bug fixes.

A bug was introduced in the last version wherein some actions were restricted under evaluation license. That is now fixed.

• It is now possible to include some of the macros in your Confluence templates
• It is now possible to add release announcements on Jira Service Desk customer portals
• Bug fixes
  • Inserting large images was breaking the template

• Bug fixes
  • Font change breaks the template
  • Custom message for empty result set not displayed

• New feature that lets you group data in release notes based on any issue attribute is now available.
• Minor bugs fixed which caused the confluence page creation to fail.

• It is now possible to publish release notes blog on Confluence
• Bug fixes
  • Couple of corner cases were reported where Confluence page creation failed, those are now fixed

• ARN is now compatible with Jira 7.11.0
• Release notes can now be generated in JSON format
  • Soon it will be possible to POST this JSON data to a pre-defined url
• It is now possible to suppress release notes generation if none of the JQL sections return any result
• Whenever issue type was included in the JQL section the Confluence page create action threw an error that page already exists, that is now resolved.
• Minor issue in rule execution logging

• Jira 7.10.0 compatibility
• App permissions compatibility with earlier versions of Jira 7.x
• Bug fix related to a conflict in tinymce editor from another add-on.

• Now generate release notes in markdown format
• Access tab removed & project level permissions added for 'Manage automated release notes'
• Minor fixes

• Versions can be now filtered based on whether they are released or not.
• Bug fixed that caused some of the versions to not appear in search results.
• Minor bug fixes

• It is now possible to trigger ARN rules via webhooks
  • This will help you integrate ARN with other devops tools
• Minor bug fixes

• Confluence integration
  • Labels were not getting created when using Confluence templates, this is now fixed.
• PDF templates
  • Warnings/errors displayed at the right places if google chrome is not installed on your Jira server (google chrome is required in order to generate release notes in pdf format)
• Template sharing across projects
  • Templates are now created as either 'Local' or 'Global'
  • Global templates can be used in rules of any projects but can be modified only within the parent project

• Ability to add labels while creating a page in Confluence

• A bug was introduced in the last release due to which JQL sections became uneditable. It was also not possible to add new JQL sections.

It is now fixed.

We strongly recommend to upgrade to this version.

• Action to publish release notes to Confluence
• Improvements in pdf generation

• Issue that prevented release notes generation in pdf format is now resolved.

Logs are added to investigate pdf generation issue on some instances.

• With this release, it is now possible to generate release notes in pdf format & send them as an attachment to email.
• Minor bug fixed that caused issues in loading images within release notes emails.

• Some custom fields were not being replaced with correct values when sequential layout was used. That is now fixed.

• Sequential formatting enhanced in release notes templates
• Fixes to make the app compatible with Oracle DB

• Mail templates now allow inserting images, tables
• ARN page access can now be configured to allow access to users who are not project administrators

Some of the enhancements released in 1.5.5 version were not available because of the faulty build, that is now corrected.

• Insert JQL section button was disabled if the Jira instance had Zephyr installed, that is now fixed
  • Irrespective of what add-ons your Jira has, this will work correctly
• Ability to remove ARN branding from templates

• Template builder now has more flexibility for JQL sections & variables
• JQL sections can be further customised
  • messages on empty results
  • display labels
  • key, id, summary - links
  • & so on
• Logs
  • All the instances of rule execution are automatically stored under logs, along with the generated emails

• Rules & Actions introduced
  • This allows you to take multiple actions (send multiple emails) in one rule
  • One project can now have multiple different release notes email templates
• Triggers to invoke the rule
  • Version release in Jira
  • Manual
  • Scheduled
• All existing email templates should be automatically migrated to 'Default Template' after this upgrade

• Some versions were not appearing in the search results, that bug is now quashed.
• When copy pasting JQL, search results were not returned properly. That is now resolved

• Email generation at the time of version release was breaking, fixed with this release

• Now configure Jira groups as email receivers
• Date format is picked from Jira setting
• Sprint parameter is retrieved correctly
• Now the sequential layout is also available in addition to tabular one
• Minor bug fixes

• When issue types involved special characters, the query didn't return any results. Now special characters are handled.

• Automated Release Notes is now compatible with Jira 7.2
• Bug fixed that caused issues when a custom field was saved in the email template.

A bug which occurred when special characters were part of the issue summary/description is resolved. Almost all the special characters are supported now.

• Maintain different templates for different projects.
• Easily customise templates with the help of JQL & custom written variables.
• Automate the process of emailing release notes every time a version is released in Jira.