Release Notes

“Support cleanup through site health reports” feature PREMIUM

• Purpose - The Site Health Reports feature is designed to give administrators visibility into the state of their Jira or Confluence instance — identifying misconfigurations, redundancies, unused elements, and inconsistencies.

• Supporting cleanup actions through these reports directly enhances system performance, governance, and usability.

• Impact

  • Enable Data-Driven Cleanup: Provide actionable insights so admins can make informed cleanup decisions.

  • Reduce Configuration Bloat: Highlight inactive or duplicate configurations (e.g., custom fields, workflows, schemes).

• Use cases:

  • Improve Instance Performance: Help clean unused elements that slow down performance.

  • Identifying Unused or Redundant Configurations: The health report flags these as cleanup candidates and supports bulk deletion.

  • Pre-Migration Preparation: Cleanup via health reports ensures only necessary and active configurations are migrated.

“Object schema duplicate copy with live object restoration” feature

• Purpose - Create exact copy of schema on same site as well as on different site along with its configurations and objects.

• Impact

  • Operational Continuity – Maintain consistent asset tracking and relationships when restructuring teams or processes.

  • Live Migration – Ensures active data (objects) is moved in real time, reducing downtime and avoiding manual data entry.

• Use cases:

  • Cross-Site Expansion – Supports smooth transfer or duplication of asset data between different Atlassian sites.

  • Restructuring or Refactoring Schema - Duplicate schema and migrate live objects into a new, improved structure, then switch usage gradually.

  • Avoiding Downtime During Maintenance - Duplicate the schema and migrate objects live to minimise downtime or disruptions to operations.

  • Audit and Compliance - Create a duplicate with all objects to preserve the current state in a read-only or backup format.

“Microsoft Azure Blob Storage for backups” feature

Purpose

Supporting Azure Blob Storage as a backup destination provides organizations with flexible, scalable, and secure options for storing their Jira or Confluence data backups. It enhances control, compliance, and reliability in managing critical business data.

Impact

• Enhanced Security – Enables use of enterprise-grade Azure security features like encryption at rest, private endpoints, and RBAC (role-based access control).

• Control Over Backup Data - Store backups in its Azure Blob Storage account, under its own governance and access policies.

Use cases

• Disaster Recovery and Redundancy - Use Azure Blob Storage as an offsite disaster recovery location with geo-redundancy options.

• Bring Your Own Storage (BYOS) – Allows organizations to store backup data in their own Azure cloud, maintaining full ownership and control.

• Supporting Azure Blob Storage for backups empowers organizations to control, secure, and scale their backup data storage in line with their cloud strategy and compliance needs.

“Xray Plugin” backup feature PREMIUM

• Purpose - Backing up Xray data—such as test cases, test plans, test executions, and test run is essential for ensuring continuity, compliance, and recovery in test management workflows within Jira.

• Impact

  • Data Protection – Safeguards critical testing artifacts from accidental deletion, corruption, or system failure.

• Use cases:

  • Analyzing Past Testing Trends - Xray backups provide access to previous versions of test cases, executions, and plans.

  • Audit & Compliance – Maintains a record of test execution history for regulatory or quality audits.

  • Ensuring Business Continuity - Xray backups help recover test management data with minimal downtime.

Improvement in “Issues” backup feature - Backup of issues linking PREMIUM

• Purpose - Backup Issue Linking ensures that relationships between Jira issues. It helps maintain project integrity, workflow continuity, and historical context when restoring data.

• Impact

  • Restoring Projects Without Losing Links - When restoring a project from backup, issue links (e.g., "blocks," "relates to," "duplicates") remain intact, ensuring dependencies are not lost.

  • Cross-Project Issue Linking - If issues are linked across different projects, backing up these links helps retain associations when restoring specific projects.

• Use cases:

  • Disaster Recovery - In case of data loss or corruption, restoring issue links ensures teams can quickly regain project dependencies and references without manual re-linking.

  • Cloning and Migration - When migrating or cloning a project, preserving issue links ensures workflows and reporting structures remain unaffected.

  • Audit and Compliance - Backup of issue links helps maintain historical records for audits, ensuring that issue relationships are verifiable even after data restoration.

Improvement in “Cross site connection + Disaster recovery” feature - Add validations in site URL

• Purpose - The validation ensures that users enter the complete and correct site URL, starting with "https://", to prevent errors and ensure a secure connection.

• Use cases:

  • Avoiding incorrect or incomplete URLs.

  • Ensuring compatibility with system requirements.

  • Enhancing security by enforcing HTTPS for encrypted connections.

  • Preventing connection failures during authentication or data transfer.

“Access Control” feature

• Purpose - App Access Control is designed to restrict and manage user access to an app within Jira or Confluence. It ensures that only authorized users or groups can interact with the app, enhancing security, compliance, and data privacy.

• Impact

  • Security – Prevents unauthorized access to sensitive features or data.

  • Granular Permissions – Allows admins to define which users or groups can access the app.

  • Compliance – Helps organizations enforce access policies based on security requirements.

  • Improved User Management – Ensures that only relevant teams can use specific app functionalities.

  • Types of clone jobs - Need clone requestor and clone approver permissions to trigger clone job for Assets configurations, Jira configurations,project clone and cleanup action job.

• Use cases

  • Role-Based Access in a Large Organization - Use Role-Based Access Control (RBAC) to ensure each department sees only relevant data.

  • Securing Third-Party App Integrations - Use access control to grant app permissions only to relevant teams, preventing unauthorized usage.

  • Temporary Access for External Users - Use access control to grant temporary permissions, revoking them when the contract ends.

  • Preventing Unauthorized Configuration Changes - Access control ensures that only authorized administrators can make system-wide changes.

Improvement in “Notifications“ - Deleted issues notifications for specific projects

• Purpose - The Deleted Issues Notifications feature alerts project admins when issues are deleted from specific projects. This helps maintain transparency, accountability, and data integrity by ensuring that issue deletions are monitored.

• Impact

  • Accountability & Auditability – Tracks who deleted an issue and when.

  • Prevention of Accidental Data Loss – Alerts admins in case of unintended deletions.

  • Compliance & Security – Helps in regulated industries where issue deletion needs oversight.

• Use cases

  • Monitoring Critical Project Issues - A project manager overseeing high-priority projects wants to be notified if any issues are deleted.Enable deleted issue notifications for critical projects to track and prevent.

  • Compliance & Audit Requirements - Notifications help maintain audit logs and ensure compliance with data retention policies.

  • Preventing Accidental or Unauthorized Deletions - Immediate notification allows quick restoration before data is permanently lost.

Improvement in “Jira issues backup“ - Can include / exclude new projects issues backup

• Purpose - User can include / exclude new projects’s issues backup from settings. This ensures that only relevant data is backed up, optimizing storage, performance, and compliance.

• Impact

  • Storage Optimization – Avoids unnecessary backups of test or temporary projects.

  • Backup Customization – Allows selective backup of critical projects only.

  • Performance Efficiency – Reduces backup execution time by excluding irrelevant projects.

• Use cases

  • Managing Large-Scale Jira Instances Efficiently - A company with hundreds of projects wants to manually approve which projects get backed up.

  • Excluding Temporary or Test Projects from Backup - Some teams in organization creates multiple test projects that don’t need backup. Set the backup to exclude new projects by default, avoiding unnecessary data storage.

Introduced “Revyz Data Manager for Jira - Bring your own storage” app

Purpose

• The Bring Your Own Storage (BYOS) feature allows organizations to use their preferred cloud storage provider (such as AWS S3) for backing up and restoring Jira data.

• This provides greater control, security, and compliance over data storage while integrating seamlessly with the organization's existing infrastructure.

Use cases

• Storing Jira Backups in a Company-Owned Cloud Storage ☁ - An enterprise wants all Jira backups to be stored in its AWS S3 bucket instead of a third-party storage service.

  • Benefit: Full control over storage, better security policies, and cost optimization.
    

• Meeting Data Residency & Compliance Requirements 📜 - A company operating in the EU must store data within a specific geographic region to comply with GDPR.

  • Benefit: BYOS ensures data residency compliance by allowing storage in chosen regions.
    

• Reducing Storage Costs by Using Existing Infrastructure 💰 - A business already has a corporate Amazon Cloud Storage account and doesn’t want to pay extra for external backup services.

  • Benefit: Saves costs by utilizing existing storage contracts.
    

• Faster Data Recovery & Reduced Downtime ⚡ - A large company needs quick recovery of Jira issues, assets, and configurations after an outage.

  • Benefit: Storing backups in on-prem or nearby cloud regions ensures faster restores.
    

• Improving Security by Keeping Backups Within Internal Storage 🔐 - Ensures end-to-end encryption and access control policies set by the company.