Fixed: Custom Variable Replacement in JQLs

We fixed an issue where custom variables weren’t replaced correctly in the JQL of a JQL section or Stats macro, particularly when used inside double quotes.

Bug

🔧 Forge migration for absolute S3 object paths

We’ve enhanced the Forge migration process to ensure S3 resources remain accessible after data migration.What’s New?

• Migrated existing relative S3 object keys to absolute paths before Forge SQL migration.
• Updated affected records across tables that store S3 object references, including widgets and templates.
• Ensured newly migrated data uses absolute S3 paths without relying on client-specific information.

Story

🔧 Forge migration for Text, Markdown, and JSON file generation APIs

We’ve migrated the Markdown, and JSON file generation APIs from Connect to Forge while preserving the existing behavior and output formats.What’s New?

• 🔧 Migrated Markdown and JSON log generation to Forge.
• 💾 Preserved existing file generation behavior and output formats.
• 🔗 Updated internal services to use the new Forge implementations.

Story

🐞 Bug fix: Preserved large template bodies after chunked uploads

We’ve resolved an issue where large templates exceeding the inline request size limit could be saved without their template body. These templates use chunked uploads during the save process, but the uploaded content was not being correctly processed.Fixes included:📥 Large template content uploaded in chunks is now correctly reassembled before saving.💾 Templates exceeding the chunking threshold retain their complete body after saving.✅ Reopening large templates now displays the full template content without the “Body required” error.🧩 Templates with both large and small bodies now behave consistently.

Bug

🔧 Forge migration for sprint event triggers

We've migrated Sprint event triggers from the Connect platform to Forge, enabling sprint-based automation to run using Forge's native event framework. This ensures sprint workflows continue to execute reliably while aligning with the Forge architecture.

Story

🔧 Forge migration for public webhook rule trigger APIs

We've migrated the public webhook rule trigger APIs to the Forge platform, enabling webhook-triggered rule executions to operate through the Forge architecture while maintaining a seamless automation experience.

Story

🔧 Forge migration for version event trigger APIs

We've migrated the Version Created and Version Released event triggers from the Connect app to Forge, enabling automated release workflows to run natively on the Forge platform.Version events are now processed using Forge event triggers with asynchronous execution, ensuring rules are triggered reliably whenever a version is created or released.

Story

🔧 Forge migration for scheduled rule execution APIs

We've migrated the Scheduled before N days of release and Scheduled at interval rule execution APIs from the legacy Java Quartz scheduler to the Forge platform.As part of this migration, scheduled rule execution now uses Forge-compatible scheduling mechanisms, ensuring automated rules continue to execute reliably within the Forge architecture.

Story

🔧 Forge migration for Run Rule and Preview Template APIs

We've migrated the remaining APIs required for the Run Rule and Preview Template workflows to Forge, ensuring these actions continue to work seamlessly within the Forge architecture.

Story

🔧 Forge migration for remaining rule and cross-service APIs

We've continued the Forge migration by moving the remaining APIs required for rule management and cross-project functionality. This update further reduces reliance on legacy Connect endpoints and improves overall platform consistency.

Story

🐞 Bug fix: Improved attachment mapping in Logs export

We've resolved an issue where attachment file names were not displayed under their corresponding attachment columns in the exported Logs report.Fixes included:

• Attachment file names are now correctly mapped to their respective columns in the exported Logs file.
• All supported attachment types are displayed in the appropriate columns for easier review and auditing.

Bug

🐞 Bug fix: Improved international character rendering in Confluence templates (New Editor)

We've resolved an issue where special international characters were not rendered correctly in Confluence (New Editor) templates. In some cases, characters with accents or diacritics were displayed as HTML entities instead of their intended Unicode characters when generating Confluence pages.This issue affected both Sequential and Table layouts.Fixes included:✅ Correct rendering of German umlauts and special characters (for example, ü, ö, ä, ß).✅ Proper decoding of HTML entities before publishing content to Confluence.✅ Consistent character rendering across both Sequential and Table template layouts.✅ Improved support for a wide range of international characters, including languages such as German, French, Spanish, Portuguese, Italian, Swedish, Norwegian, Danish, Finnish, Icelandic, Polish, Czech, Slovak, Romanian, Turkish, Hungarian, Croatian, Serbian, Lithuanian, Latvian, and Estonian.

Bug

🔧 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