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.

👤 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. ✅

⚙️ 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 🕒

Open

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.

Open

🚀 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. ✨

Open

🐞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 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 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 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 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 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 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.,

,
,

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

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

🔄 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 ☁️🚀.