Data Migration to Atlassian's Forge

We have been migrating ARNR app to Atlassian's forge platform incrementally for last few weeks. This update marks the last and major update. Through this update, all of your existing data within ARNR data would be migrated to Atlassian's Forge infrastructure from our infrastructure. Data migration might take some time and app will not be accessible during this time. Your existing data remains untouched and safe. Users will observe no change in app's functionality and behaviour post migration.

If you observe any issue during or after migration, please contact our support team here

Read more about Forge Migration here.

Epic

Corrected default field configuration on Release pages ✅

Fixed a sporadic bug that left the release page in an odd UI state and stalled backend loading.

Bug

Default option now correctly shown in custom variable list✅

Fixed a bug where default values for single-select and multi-select custom variables weren’t showing in lists. They now display correctly.

Bug

Corrected Jira link base URL so all links open correctly 🔗✅

Jira issue links were pointing to the wrong base URL. They now use the correct one.

Bug

Ensured the From address is accurate on outgoing emails 📧

Emails for Release page subscriber alerts, log exports, and send‑email rule actions were going out from the wrong address. They now use default sender.

Bug

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