📌 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: 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

🛠️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

🛠️ Fix: Confluence space and template selector issues resolved

We’ve fixed a issue in the Publish to Confluence (new editor) action to make rule creation smoother and more reliable:✅ What’s fixed:

• Space selector binding issue – Previously, when selecting a space from the source template dropdown, the choice didn’t reflect immediately. Users had to select the space twice for it to appear. This is now resolved — your first selection will be retained.

This improvements ensure a seamless experience when creating or editing Confluence rule actions. 🚀

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

🔐 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 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

🛠️ 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

🎬 Generate and share video reports with ease

We’ve introduced new video reports in ARNR , upload it to our secure servers, and send you a download link straight to your inbox ✉️✨. Here’s what’s new:

• 📌 Create “Video” report template – easily select video to create a video template.



• 📩 Generate video action – Add a rule action to your rules to generate and share video report via email with a secure download link.

With this update, you can generate AI powered video reports for your stakeholders 🎉

Bug

✉️ 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

🛠️ 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