GitProtect v2.0.0

🆕 NEW FEATURES

Jira Automation Rules

We have expanded our Atlassian ecosystem support with full backup and restore capabilities for Jira Automation Rules — an essential Jira feature enabling advanced process automation (e.g., automatically adding comments to tasks that have remained in a specific status for more than X days). Automation Rules can now be protected as part of your Jira organization backup plan. When creating or editing a backup plan, simply navigate 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, allowing you to restore individual rules or project-specific rules.

Credential rotation during GIT backup

We’ve enhanced our Git SaaS backup capabilities by introducing automated credential rotation. If API throttling is detected, the system can seamlessly switch to alternative credentials (GitHub Apps, 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 instead of modifying existing ones.

Bitbucket - pull request description restoration

Full restoration now includes the original description text.

Ability to exclude repositories from Azure DevOps backup plan

You can now exclude specific repositories from a backup plan, just like in GitHub, GitLab, and Bitbucket.

Improvements to the reauthorization of GIT organizations integrated with PAT

Added token expiration detection, improved re-authorization UI, and email notifications for expiring tokens (enabled by default for new integrations).

Git Repository Filter by backup status

Repositories can now be filtered by backup status.

🐛 BUGFIXES

GitHub - Protection Issue > 10,000 (10k) Issues

Correct handling backup of repositories with more than 10,000 issues.

Bitbucket - incorrectly set source branch in restored pull request

Corrected source branch mapping for restored pull requests.

Backup and restore issues after rename project in Azure DevOps

Fixed backup and restore issues after project name changes.

Problem with restoring deleted attachments in Jira

Corrected granular restore of deleted attachments.

Problem with restore from Azure DevOps to GitHub organization integrated by GitHub App

Fixed restore compatibility.

GitLab - distabling additional functionalities in the repository causes errors in the back task

Backup now skips disabled repository features without triggering warnings.

Incorrect default branch and resource count in summary after restoration repository to local device

Restored repositories now set the correct default branch and display accurate LFS file counts.

GitLab - closed milestone recreates as open

Closed milestones are now restored with the correct “closed” status.