Atlassian ecosystem support has been expanded to include full backup and restore for Jira automation Rules, a key feature for advanced process automation, such as automatically adding comments to tasks in a specific status for a set number of days.
Automation rules can now be included in your Jira organization backup plan. When creating or editing a plan, go to Data to protect > Additional data and select Automation rules.
Restoration is available both as part of a full organization recovery (disaster recovery) and in granular mode, enabling the recovery of individual rules or project-specific rules.
Git SaaS backup capabilities have been enhanced with automated credential rotation. If API throttling occurs, the system can automatically switch to alternative credentials (GitHub Apps or user accounts), improving backup performance and reliability.
Backup summaries now include:
A list of all credentials used for the task.
A throttling history with timestamps and total blocked duration.
When restoring links between Jira assets objects and Jira work items, new custom fields are now created rather than modifying existing fields.
Full restoration now preserves the original description text.
You can now exclude specific repositories from a backup plan, consistent with the functionality in GitHub, GitLab, and Bitbucket.
Token expiration detection has been added, along with an improved re-authorization interface and email notifications for expiring tokens, enabled by default for new integrations.
Repositories can now be filtered based on their backup status.
Backup of repositories with more than 10,000 issues is now handled correctly.
Source branch mapping for restored pull requests has been corrected.
Backup and restore issues caused by project name changes have been fixed.
Granular restore of deleted attachments has been corrected.
Restore compatibility issues have been fixed.
Backup now ignores disabled repository features without generating warnings.
Restored repositories now have the correct default branch and show accurate LFS file counts.
Closed milestones are now restored with their correct closed status.