🔎 Staying on top of your release schedule just got easier!
The Calendar tab got an upgrade and is now called Gadgets.
Alongside your familiar Release Calendar, we have added a brand new gadget: Releases per Month 📊 . It gives you a quick snapshot of your team’s release cadence over the past 12 months, making it simple to spot trends and check consistency at a glance.
Have ideas for other gadgets that would help your team plan and track even better? We’d love to hear what you think!
Note: Currently available in the in-project view, with cross-project support coming soon.
Bug fix: Issues on Release Pages are not sorted correctly
We’ve resolved an issue where issues on Release Pages were not displayed in the sorting order as specified in the JQL query. Issues now follow the sorting order as configured in JQL, making it easier to view release information as intended ✅.
Bug fix: Incorrect navigation from Calendar gadget
🛠️ Fixed a bug where issue links from the Calendar opened a broken URL and showed “No project available.” Now those links redirects to the right release version ✅.
We fixed an error blocking access to the some restricted releases pages 🔒
We’ve fixed a bug that blocked users from getting magic link after entering email for some restricted Release Pages. Now user can sign in and access it.
Issue keys now display correctly in release notes 🎯
Fixed a bug where issue keys didn’t show up in release notes when Jira’s default language was German. They now display correctly.
Custom variable values now replaced correct during rule runs 🎯
We fixed a bug where rules ignored the default value for a custom variable if no value was set. Now rules automatically use the default value when not configured.
Tightened widget permissions across projects to keep access secure 🔒
Fixed a security bug where some users could view or edit widgets from other projects without permission. We now properly check permissions, so only authorized users can access or change widgets.
Template preview failed when date-picker type of custom variable used🎯
Template previews could fail if template included a date-picker type of custom variable. It’s now fixed.
Fixed: Forge migration failing when migrating ARNR widgets data ✅
We have fixed a bug that caused Forge migrations to fail when moving some ARNR widget data. Migrations should now run smoothly.
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.
Email content now shows in Logs preview 🎉
Fixed the bug that showed empty email content in Logs preview. Content now displays correctly.
Fixed broken subscription confirmation link in emails ✅
Some subscribers hit a dead end with the subscription confirmation link. We’ve fixed it. Confirmation link email is now sent properly.
Fixed webhook-triggered rules not running after Forge migration ✅
Squashed a bug that stopped rules with valid webhook URLs from firing after Forge migration. Webhook triggers now run properly.
Fixed wrong rule execution limit showing for free app users 🎯
Squashed a bug that told ARNR free app users they’d hit their rule execution limit. The app now shows the correct status.
Template background images were broken after Forge migration, now fixed 🎉
Fixed a bug that broke background images in PDF and Word templates after the Connect to Forge migration. Images now render correctly.
Fixed default field setup on Release pages 🛠️
Fixed a sporadic bug that left the release page in an odd UI state and stalled backend loading.
Default option now displays correctly 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.