👤 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

🚀 Migrate settings and configuration module to Atlassian Forge

We’ve upgraded our settings and configuration module to run on Atlassian Forge. ⚙️✨It might require manual upgrade on your current instances.

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:

1. Link types to include – Select specific issue link types (e.g., blocks, is blocked by, developed by) to display in your reports. If none are selected, all linked issues will be shown by default.
2. Hide link type label – Choose to hide link type labels and display only the linked issue keys in a clean, unified list.

These options give you finer control 🎯 over which linked issues appear and how they’re presented helping you create more focused, readable, and customized reports 📝.

Story

🐞 Bug fix: Confluence (New Editor) draft template now opens in the correct space

We’ve fixed a bug 🐛 where creating a Confluence (New Editor) template didn’t redirect to the selected space with the draft template. Instead, users were being redirected to the Confluence home page, ignoring their chosen space. 🏠With this fix, when you create a draft template and select your desired instance and space, the system will now correctly open the draft page in that specific space. 📄✨

Bug

🐞 Bug fix: [versionDriver] variable now gets replaced correctly in scheduled rule executions

We’ve fixed a bug 🐛 where the [versionDriver] variable in templates was not getting replaced with its value when a rule was triggered via a scheduled trigger (e.g., hourly or daily runs). ⏱️Previously, this caused actions depending on the [versionDriver] variable to display incomplete information during scheduled executions.

Bug

🐞Bug fix: Scheduled rules now resume automatically after being re-enabled

We’ve fixed an issue where scheduled rules did not resume execution after being disabled and then re-enabled from the Rule Listing page. ⚙️Previously, even after re-enabling a rule, it wouldn’t run again until the rule was manually opened and saved causing missed executions.Rules will now automatically resume from the next applicable schedule as defined by the cron configuration. ✅

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

✨ 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

🛠️ Bug fixes and improvements

🖼️ Images in Confluence pages
Fixed an issue where Jira attachment images were not always displayed correctly in Confluence. Images will now publish more reliably.🔑 Authentication handling
Improved the way access tokens are managed to make the app more efficient and stable. 🚀

Bug

🛠️ Bug fix: [versionDriver] variable in scheduled triggers

We fixed an issue where the [versionDriver] variable was not being replaced correctly when rules were triggered using “Scheduled before N days of release”.✅ The variable now works as expected in scheduled triggersWith this fix, your scheduled release notes and reports will always display the correct version driver. 🚀

Bug

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

📌 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