GitProtect 2.0.0
🆕NEW FEATURES
Jira automation rules
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.
Credential rotation during Git backup
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.
🔨 IMPROVEMENTS
Jira assets objects linking
When restoring links between Jira assets objects and Jira work items, new custom fields are now created rather than modifying existing fields.
Bitbucket — pull request description restoration
Full restoration now preserves the original description text.
Ability to exclude repositories from Azure DevOps backup plan
You can now exclude specific repositories from a backup plan, consistent with the functionality in GitHub, GitLab, and Bitbucket.
Improvements to the reauthorization of Git organizations integrated with PAT
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.
Git repository filter by backup status
Repositories can now be filtered based on their backup status.
🐛 BUGFIXES
GitHub — protection issue > 10,000 (10k) issues
Backup of repositories with more than 10,000 issues is now handled correctly.
Bitbucket — incorrectly set source branch in restored pull request
Source branch mapping for restored pull requests has been corrected.
Backup and restore issues after renaming project in Azure DevOps
Backup and restore issues caused by project name changes have been fixed.
Problem with restoring deleted attachments in Jira
Granular restore of deleted attachments has been corrected.
Problem with restoring from Azure DevOps to GitHub organization integrated by GitHub App
Restore compatibility issues have been fixed.
GitLab — disabling additional functionalities in the repository causes errors in the backup task
Backup now ignores disabled repository features without generating warnings.
Incorrect default branch and resource count in summary after restoring a repository to local device
Restored repositories now have the correct default branch and show accurate LFS file counts.
GitLab — closed milestone recreates as open
Closed milestones are now restored with their correct closed status.
Last updated