Automated Release Notes & Reports app for Jira

8.3

APR 26

🔄 Adopted new DC to Cloud Migration Listener

We’ve updated our DC to Cloud migration listener to align with Atlassian’s latest recommended approach. By moving to the new discoverable listener, we ensure continued compatibility, improved reliability, and a future-ready migration experience ☁️🚀.

Task

Linked Issues field configuration now available in Spotlight & Helper app 🔗✨

The Linked Issues field now supports additional configuration options in both the Spotlight variable section and the Helper app (Confluence templates) 🎯
You can configure settings like link types to include and hide link type labels, bringing it in line with other supported fields and making customization clearer and more consistent across templates and the Confluence editor.

Story

👤 Improved handling for missing user details in rule and template listings

We’ve enhanced the Rule Listing and Template Listing pages to ensure better clarity and consistency. Previously, if the user details were missing, the Created by or Last modified by fields appeared blank or broken. Now, in such cases, you’ll see “No user found” displayed instead. 🙌 This update improves the overall readability and ensures your listings always look clean and informative. ✅

Story

⚙️ Enhanced Comment Controls for ARNR Reports

The Comments feature in ARNR just got smarter. While comments were always supported, you can now fine-tune how they appear in your reports to better match your team's needs and reporting style. 🔧 What’s Improved

“Number of Comments” setting → choose how many recent comments to include (up to 10)
Optional timestamp display → show or hide the comment creation date 🕒

Story

You can now customize how linked issues appear in your reports! 🎉

We’ve added two new configuration options under JQL → Fields → Linked Issues → ⚙️ Additional Configuration: You can now select specific issue link types. Example blocks, is blocked by, developed by to display in your reports. If none are selected, all linked issues will be shown by default. Also, you can hide link type labels and display only the linked issue keys in a clean, unified list.

Story

🚀 Enhanced AI Generator: Support for multiple input fields

We’ve upgraded the AI Generator macro in ARNR Template Builder to give you more powerful and flexible inputs for generating summaries. You can now:

Select from a wider range of Jira field types, including:
- Single-line & multi-line text
- Number, date, and date-time
- User picker
- Custom fields
Choose up to 3 Jira fields as AI inputs using a new multi-select dropdown.

This means richer context for the AI and more accurate, detailed summaries across all the templates. ✨

Story

🐞 Bug fix: Issues in DC to Cloud Migration

We’ve fixed issues that caused incomplete data migration and broken references during ARNR migrations from Data Center to Cloud.Fixes included:

✅ Resolved missing migration of critical data (Rules, Rule Actions, Integrations)
🔗 Fixed incorrect handling of DC IDs by applying proper DC → Cloud ID mapping (users, projects, custom fields)
🧩 Fixed template visibility issues caused by project mapping mismatches

Result:

Restored functionality of rules and automations post-migration
Eliminated broken references and data inconsistencies
Reduced need for manual fixes after migration

In-sprint Bug

🐞Bug fix: Improved OAuth token handling for Confluence Integration

We’ve resolved an issue that could prevent saving Confluence integrations due to OAuth token size limitations. This update ensures tokens are stored reliably, allowing seamless reconnection and uninterrupted integration setup 🔄

Bug

🐞Bug fix: For Stats Macro editing issue after DC to cloud migration

We’ve resolved an issue affecting the Stats macro in certain templates migrated from Data Center to Cloud.In some cases, when editing the Stats macro within imported templates, the screen would turn blank and the app would become unresponsive. ✅ What’s fixed?

The Stats macro now works smoothly in both preview and edit modes
No more blank screens while editing
Improved stability for templates migrated from Data Center to Cloud

Bug

🐞 Bug fix: Corrupted Word file generated by Specific API URL Format

We’ve fixed an issue where certain API URLs in Jira descriptions caused generated Word reports to become corrupted or fail to download.✅ Fix

All URLs are now handled safely during Word generation
Reports download and open correctly

Bug

🐞Bug fix: Improved reliability for Confluence rule execution with large data

We’ve resolved an issue where Confluence rule actions could fail with a “Could not invoke remote call” error when processing large templates. Rule execution is now more stable and consistent, even with larger data volumes, ensuring a smoother publishing experience.

Bug

🐞 Bug fix: Group By variables with formatted non-English text now work correctly

Fixed an issue where Group By variables containing foreign-language or Unicode characters failed validation when formatting (bold/italics) was applied. The system now correctly recognizes formatted variables, allowing templates to save and execute without errors across all languages ✅

Bug

🐞 Bug Fix: Sprint Selector no longer shows up in variable selector when not used in template

Resolved an issue in ARNR templates where the Sprint Selector appeared in the variable selector when the user Previews the template or executes the Rule even when the template did not use Sprint variables.
Now, the selector is displayed only when Sprint variables are included in the template and stays hidden otherwise. ✔️🎯

Bug

🐞Bug Fix: Issue Descriptions in PDFs Now Render Correctly for Scheduled Triggers

When a PDF rule was executed through a scheduled trigger, the issue description appeared in the PDF as raw HTML (e.g., <p>, <br>, <ul>) instead of properly formatted text.We’ve resolved this behavior.✅ What’s Fixed

PDFs generated from scheduled rule executions now correctly render the formatted issue description.
No more raw HTML tags in the output.

Bug

📄 Support custom variables in PDF template title, last page, and header/footer sections

🎉 You can now use custom variables in the title page, last page, and header/footer sections of your PDF templates just like in Word templates.In the Advanced Settings section you can now manually add custom variables, and they’ll be correctly replaced with the expected data when generating PDFs. ✨

Bug

8.2

APR 26

🐞 Bug fix: Issues in DC to Cloud Migration

We’ve fixed issues that caused incomplete data migration and broken references during ARNR migrations from Data Center to Cloud.Fixes included:

✅ Resolved missing migration of critical data (Rules, Rule Actions, Integrations)
🔗 Fixed incorrect handling of DC IDs by applying proper DC → Cloud ID mapping (users, projects, custom fields)
🧩 Fixed template visibility issues caused by project mapping mismatches

Result:

Restored functionality of rules and automations post-migration
Eliminated broken references and data inconsistencies
Reduced need for manual fixes after migration

In-sprint Bug

8.1

APR 26

🔄 Adopted new DC to Cloud Migration Listener

Task

8.0

MAR 26

Jira version 11.3 compatibility ✔️

ARNR is now compatible with Jira version 11.3 and below.

Story

7.9

OCT 25

✉️ Improved email delivery

We’ve enhanced our email system to ensure more reliable delivery and smoother configuration. Emails will continue working as expected No action needed on user side.

Story

🔐 Strengthening app security with Forge authentication

We’re upgrading our apps to use Forge authentication instead of storing API tokens. This change aligns with Atlassian’s updated security standards ✅ and ensures stronger protection of your data 🔒.

As Atlassian is deprecating basic authentication after September 30, 2025. All users using API tokens need to reconnect their Confluence instance using the new OAuth method.

Story

✨ New Confluence templates in template gallery

We’ve added more ready-to-use Confluence templates in template gallery so you can publish and share information faster 📝. With this update, you’ll now find Confluence versions of the following templates ✅ Newly added templates:

📊 Sprint review report
📦 Version workload report
🗓️ Release planning report
🐞 Bug tracking and resolution report
🤝 Weekly customer support report
🚀 Daily stand-up report

Story

🚦 New limits introduced to improve rule performance

To make sure your rules run faster and more reliably, we’ve introduced a few sensible limits:

✨ Rule actions: Max 10 (Free app/Standard edition) and 15 (Advanced edition). Existing rules above this will continue working, but you can’t add more actions.
⏰ Cron schedules: Minimum interval is now 1 hour. Existing rules with shorter intervals will keep running but can’t be saved again with <1 hour.
📊 JQL fetch: Max 250 issues (Free App/Standard edition) and 500 issues (Advanced edition). You’ll see an error if you try to set a higher limit.

These updates help maintain performance, avoid delays, and give you a smoother experience ⚡

Story

📌 New: Automatically link Confluence pages in Jira releases

We’ve introduced a new Jira operation action that makes it easier to keep your project documentation and releases in sync 🎉Now, when you publish a Confluence page through ARNR, you can automatically link them to the Related Work section in Jira Releases. This helps your team quickly track, reference, and share important project information all in one place. What’s new:

➕ New action: Jira operation
🔗 Link related work to version: Automatically adds Confluence and Release Page links under the Related Work section in Jira
✅ Works with Confluence (New editor) action

This update makes it simple to connect your releases with the right documentation and ensures nothing gets lost between Jira and Confluence.

Story

🛠️ Fix: Rule execution and logging issues resolved

We’ve fixed an issue where Confluence rule actions were getting stuck in progress, and the executed rules did not appear in the Logs tab✅ What’s fixed:

Rule actions now execute without getting stuck.
Executed rules are correctly logged in the Logs table.
Confluence pages are generated successfully when rules run.

Bug

🛠️Fix: Description fields now populate correctly in Confluence pages

We’ve fixed an issue where description fields from the JQL section were not appearing in Confluence pages generated via the new editor.Now, when using a Confluence template with a JQL section that includes the description field, the generated page will now display the description values as expected 🚀

Bug

🛠️Fix: Projects now appear correctly in cross-project screen

We’ve resolved an issue where projects added as exceptions under “Access ARNR in-project screen” settings were not showing up in the cross-project screen. When the in-project screen is disabled for all projects but a project is added as an exception, that project will now appear and can be accessed from the cross-project screen as expected.

Bug

🐞 Bug fix: Email failures with more than 50 recipients

We’ve fixed an issue where emails sent through the default provider failed if the recipient list exceeded 50.
Now, the system automatically splits large lists into smaller batches so your notifications, release updates, and rule-based emails are delivered reliably.

Bug

🛠️ Fixed issue with AI-generated output on cross-project screen in Confluence

We have fixed a bug that was preventing users from creating AI-generated outputs in Confluence for the cross-project screen. You can now generate and publish AI-powered content without interruptions, ensuring smoother collaboration and documentation in Confluence. 📑✨

Bug

🚀 Faster app load with optimized AI setting check

Previously, the app made multiple checks for all projects when loading, which caused slow performance for customers with many projects in the AI exception list. We’ve fixed this by checking only the accessed project, resulting in faster load times and improved scalability.

Bug

🛠️Fix: Email action now supports Jira groups with special characters

We’ve fixed an issue where emails were not being delivered to users if they belonged to Jira groups with special characters in their names (e.g., #test, test#, !dev#qa).Email action will now correctly send notifications to all users in Jira groups, regardless of whether the group name contains special characters. ✉️✨

Bug

🚀 ARNR Now Compatible with Jira up to Version 10.7.4

Happy to announce that Automated Release Notes and Reports (ARNR) is now fully compatible with Jira versions up to 10.7.4!If you’re planning to upgrade your Jira instance, ARNR will work smoothly without any additional configuration.

Bug