🐞 Bug Fix: Error while generating AI suggestions using AI generator tab

We’ve resolved an issue that could cause errors when generating AI-powered release notes or summaries using a large number of issues using AI generator tab. The system now handles larger issue sets more reliably, ensuring long and detailed content is generated successfully without interruptions.

Bug

🚀 Upgraded ARNR AI Engine to GPT-5

ARNR now runs on GPT-5, enabling support for significantly larger inputs and producing smarter, richer summaries, release notes, and reports. ✨📈 Expanded Custom Prompt Limit
Custom prompt capacity has increased from 500 to 1,200 characters, allowing you to convey more detailed and contextual instructions. 📝🔧 Configurable GPT-5 Model (Advanced Edition)
Advanced users can now connect and configure their own GPT-5 model directly with ARNR for highly customized AI outcomes. 🧠⚙️🛠️ Available Across AI Features
These upgrades are applied across:

• AI Rule Action
• AI Generator tab
• AI Macro in Template Builder
• AI Template Builder

Story

📊Export ARNR usage data right from the app📥

A new Export button has been added to the Logs tab (both In-Project and Cross-Project views) to export ARNR logs from the last 90 days ⏳📤

• When used from the In-Project screen, it exports logs only for that selected project 📁
• When used from the Cross-Project screen, you can choose to export either All Projects data or only the Cross-Project data 🌐

Once the export is generated, a download link to the Excel file will be sent to the logged-in user’s email address 📧📄

Story

🐞 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

Group issues by any Jira field on Release Pages

We’ve added a new way to organize issues on your release pages, you can now group issues by the Jira field of your choice for a cleaner and more structured view. What’s new ✨

• Group by Field 2
  Use the selected Field 2 value (e.g., Issue type, Assignee, Status) as a section header.
  Issues are neatly organized under each heading, and the field is no longer repeated inside every issue card.
• Supports a wide range of Jira fields
  Including Issue Type, Status, Priority, Labels, Components, Assignee, Reporter, Versions, Sprint, Dates, Story Points, Time Tracking, and more.

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

🐞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

👤 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