GitProtect v2.0.5

🆕 NEW FEATURES

Support for additional credentials during repository and Azure DevOps project restores

To better mitigate API throttling and limitations, we added support for using multiple credentials (e.g., PATs, GitHub Apps) at the organization level during restore operations for Git repositories and Azure DevOps projects. During restore task configuration, you can select which credentials to use; the system will automatically pick the most appropriate credential for each repository/project and will rotate credentials throughout the restore process. This improves restore throughput and reliability.

Restore Azure DevOps project using repositories from the same backup chain

Previously, when restoring an Azure DevOps project together with repositories, the system restored the latest available repository snapshots regardless of whether they came from the same backup as the project.

Version 2.0.5 introduces a new setting, “Restore repositories from this project’s backup” (enabled by default for backups created with this version). When enabled, repositories are restored only from the same backup chain as the project, ensuring consistency of the restored state.

🔨 IMPROVEMENTS

Faster data loading in Jira granular restore configuration

Optimized tables and metadata handling.

Re-use of existing custom fields during Jira restores

The system reuses existing fields instead of creating new ones, keeping the environment cleaner.

Extended Jira API error logging

Improved insight into issues during backup and restore.

Extended error logging for Git repository restores

More detailed messages for quicker troubleshooting.

Re-authorization process for Jira integrations affected by PAT expiry

Automatic detection, email notifications, and a simple renewal process to ensure backup continuity.

🐛 BUGFIXES

Jira Assets

Correct attribute names of label type when restoring.

Jira

Fixed issue with increasing backup times in granular backup.

GitHub Marketplace

Automatic creation of a default backup plan at first login.

GIT/ADO credentials verification

Fixed incorrect handling of accounts previously marked as invalid.

Restore task Azure DevOps summary

Corrected data in the data destination section of restore logs.