GitProtect 2.0.5
🆕 NEW FEATURES
Support for additional credentials during repository and Azure DevOps project restores
To reduce API throttling and limitations, multiple credentials (e.g., PATs, GitHub Apps) can now be used at the organization level during restore operations for Git repositories and Azure DevOps projects.
When configuring a restore task, you can select which credentials to use. The system automatically chooses the most suitable credential for each repository or project and rotates credentials throughout the restore process, improving throughput and reliability.
Restore Azure DevOps project using repositories from the same backup chain
Previously, restoring an Azure DevOps project along with its repositories would use the latest available repository snapshots, regardless of whether they came from the same project backup.
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 active, repositories are restored only from the same backup chain as the project, ensuring consistency in the restored state.
🔨 IMPROVEMENTS
Faster data loading in Jira granular restore configuration
Tables and metadata handling have been optimized.
Re-use of existing custom fields during Jira restores
The system now reuses existing fields instead of creating new ones, keeping the environment cleaner.
Extended Jira API error logging
Visibility into issues during backup and restore has been improved.
Extended error logging for Git repository restores
Error messages are now more detailed, enabling faster troubleshooting.
Re-authorization process for Jira integrations affected by PAT expiry
Automatic detection, email notifications, and a streamlined renewal process have been added to ensure backup continuity.
🐛 BUGFIXES
Jira assets
Attribute names of label type are now correctly restored.
Jira backup
An issue causing longer backup times in granular backups has been fixed.
GitHub Marketplace
A default backup plan is now automatically created at first login.
GIT/ADO credentials verification
Incorrect handling of accounts previously marked as invalid has been fixed.
Restore task Azure DevOps summary
Data in the data destination section of restore logs has been corrected.
Last updated