🔧 Forge migration for AI rule action execution APIs

We've migrated the AI rule action execution APIs to the Forge platform, maintaining the reliability and consistency of AI-powered automation within ARNR.

Story

🔧 Forge migration for Email rule action execution APIs

We've migrated the Email rule action execution APIs to Forge, ensuring email-based automation runs seamlessly within the Forge platform. This update maitains the reliability and consistency of automated email notifications while supporting the ongoing migration from Connect to Forge.

Story

🔧 Forge migration for manual rule execution and Widget, Release Page action APIs

We've migrated the manual rule execution framework and the underlying Widget and Release Page action APIs to Forge, providing a more reliable and scalable execution experience while maintaining existing rule behavior.

Story

🐞 Bug fix: Improved detection of ARNR Free app during Free-to-Paid migration

We've resolved an issue where the Free-to-Paid Migration page could incorrectly display a "Required Jira app was not found" message even when the ARNR Free app was already installed.This update ensures the application correctly detects the installed Free app and displays the migration interface when all prerequisites are met.Fixes included:

• Corrected Free app detection during the migration validation process.
• Prevented the misleading "Required Jira app was not found" message from appearing when the ARNR Free app is installed.
• Restored access to the migration workflow for eligible customers.

These improvements provide a smoother and more reliable migration experience when upgrading from the ARNR Free app to the Paid Forge app.

Bug

🔧 Forge migration for Slack and MS Teams rule action execution APIs

We've migrated the Slack and Microsoft Teams rule action execution APIs to Forge, improving the reliability and consistency of automated notifications across supported collaboration platforms.

Story

🔧 Forge migration for POST and Jira Service Management announcement rule action execution APIs

We've migrated the execution APIs for POST and Jira Service Management (JSM) Announcement rule actions from Connect to Forge, ensuring these actions run seamlessly within the Forge platform.

Story

🔧 Forge migration for Confluence action execution APIs

We've migrated the Confluence action execution APIs from Connect to Forge, ensuring that Confluence publishing and related execution workflows are fully supported on the Forge platform.

Story

🐞 Bug fix: Improved rendering of static images and Jira field icons in email notifications

We've resolved an issue where static images and Jira field icons were not displayed correctly in emails generated by the Send Email rule action, even though they appeared correctly in the Email Template Preview.Fixes included:

• Static images embedded in email templates are now rendered correctly in delivered emails.
• Jira field icons, such as the Priority icon, are now displayed when Display as text is disabled.
• Improved consistency between the Email Template Preview and the final email received by recipients.

This update ensures your email notifications maintain the intended formatting and visual elements, providing a consistent experience between preview and delivery.

Bug

🐞 Bug fix: Improved ARNR custom variable resolution in Forge template preview

We've resolved an issue where ARNR custom variables were not resolving correctly during Template Preview in the Forge app, causing JQL-based sections to display 0 results after execution.With this update, ARNR custom variables are now evaluated correctly during Forge execution, ensuring that template previews and downloaded documents accurately display the expected issue lists and counts for the selected release version.

Bug

🐞 Bug fix: Resolved template save failures for Stats & Chart macros inside JQL Section macros

We've resolved an issue that prevented templates from being saved when a Stats & Chart macro was placed inside a JQL Section macro.In certain scenarios, saving the template failed with an error indicating an invalid image source, preventing users from storing otherwise valid template configurations.Fixes included:

• ✅ Resolved template save failures for Stats & Chart macros nested within JQL Section macros.
• ✅ Ensured valid nested macro configurations can be saved successfully.

This update ensures templates containing nested Stats & Chart macros can be saved successfully, providing a smoother and more reliable template authoring experience.

Bug

🐞 Bug fix: Removed deleted rule actions from the Rules UI

We've resolved an issue where deleted rule actions could continue to appear in the Rules configuration screen even after being successfully removed.Fixes included:

• Deleted rule actions are now removed from the UI immediately after a successful deletion.
• The Rules screen now accurately reflects the current rule configuration.

These improvements provide a more reliable rule management experience and eliminate confusion.

Bug

🔧 Forge migration for individual Rule Action Preview APIs

We've migrated the individual Rule Action Preview APIs from Connect to Forge, ensuring preview experience for individual rule actions remain same.

Story

🔧 Forge migration for external email sending service

We've migrated the email sending service to Forge, providing a unified and reliable way to deliver emails across ARNR features such as Rule Actions, Rules, and Release Pages.

Story

🔧 Forge migration for Help tab Integration Status APIs

We've migrated the Help tab's Integration Status functionality from Connect to Forge.What's New?

• Integration Status APIs are now powered by the Forge platform.
• Migrated Help tab APIs for integration management and app tours, including:
  • Integration list retrieval
  • Integration status updates
  • Integration status indicators
  • App tours
  • App tour frame retrieval

Story

🐞 Bug fix: Confluence action execution is now visible in Cross Project rule logs

We've resolved an issue where Confluence actions were missing from the Logs tab after executing Cross Project rules.Previously, although the Confluence action executed as part of the rule, it did not appear in the execution logs on logs tab, while other actions were displayed correctly. This made it difficult to verify the outcome of Confluence publishing actions or troubleshoot rule executions.

Bug

🔧 Forge migration for common settings APIs

We've migrated the common Settings APIs from Connect to Forge, ensuring key application settings and user preferences are handled through the Forge platform.

Story

🔧 Forge migration for Rules APIs

We've migrated the Rules APIs from Connect to Forge, bringing rule management capabilities onto the Forge platform.

Story

🐞 Bug fix: Resolved custom variable resolution in templates

We've resolved an issue where custom variables were not functioning correctly throughout the template generation workflow. In some cases, custom variables were inserted into templates as [undefined], and the Custom Variable Selector was not displayed during Template Preview or Rule Execution, preventing users from providing values.Fixes included:

• Custom variables are now inserted into templates using the correct variable placeholder.
• The Custom Variable Selector is displayed during both Template Preview and Rule Execution, allowing users to provide values as expected.
• Generated templates now correctly resolve and display the selected custom variable values.
• If no value is provided, the configured default value is applied automatically.

This update restores reliable custom variable support across template creation, preview, and automated rule execution, ensuring templates generate with the expected content.

Bug

🔧 Forge migration for Rule Action APIs

We've migrated the Rule Action APIs from Connect to Forge, enabling rule actions to run on Atlassian's Forge cloud platform.

Story

🔧 Forge migration for Template management APIs

We've completed the migration of the Template management APIs from Connect to Forge, bringing the complete template lifecycle to the Forge platform.

Story