> For the complete documentation index, see [llms.txt](https://helpcenter.gitprotect.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.gitprotect.io/changelog/2025/gitprotect-2.0.0.md).

# GitProtect 2.0.0

### 🆕 NEW FEATURES <a href="#new-features" id="new-features"></a>

#### <mark style="background-color:blue;">Jira automation rules</mark> <a href="#new-features" id="new-features"></a>

**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.

#### <mark style="background-color:blue;">Credential rotation during Git backup</mark>

**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:

1. A list of all credentials used for the task.
2. A throttling history with timestamps and total blocked duration.

***

### ​🔨 IMPROVEMENTS <a href="#improvements" id="improvements"></a>

#### <mark style="background-color:blue;">Jira assets objects linking</mark> <a href="#improvements" id="improvements"></a>

When restoring links between **Jira** assets objects and **Jira** work items, new custom fields are now created rather than modifying existing fields.

#### <mark style="background-color:blue;">Bitbucket — pull request description restoration</mark>

Full restoration now preserves the original description text.

#### <mark style="background-color:blue;">Ability to exclude repositories from Azure DevOps backup plan</mark>

You can now exclude specific repositories from a backup plan, consistent with the functionality in **GitHub**, **GitLab**, and **Bitbucket**.

#### <mark style="background-color:blue;">Improvements to the reauthorization of Git organizations integrated with PAT</mark>

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.

#### <mark style="background-color:blue;">Git repository filter by backup status</mark>

Repositories can now be filtered based on their backup status.

***

### 🐛 BUGFIXES <a href="#bugfixes" id="bugfixes"></a>

#### <mark style="background-color:blue;">GitHub — protection issue > 10,000 (10k) issues</mark>

Backup of repositories with more than 10,000 issues is now handled correctly.

#### <mark style="background-color:blue;">Bitbucket — incorrectly set source branch in restored pull request</mark>

Source branch mapping for restored pull requests has been corrected.

#### <mark style="background-color:blue;">Backup and restore issues after renaming project in Azure DevOps</mark>

Backup and restore issues caused by project name changes have been fixed.

#### <mark style="background-color:blue;">Problem with restoring deleted attachments in Jira</mark>

Granular restore of deleted attachments has been corrected.

#### <mark style="background-color:blue;">Problem with restoring from Azure DevOps to GitHub organization integrated by GitHub App</mark>

Restore compatibility issues have been fixed.

#### <mark style="background-color:blue;">GitLab — disabling additional functionalities in the repository causes errors in the backup task</mark>

Backup now ignores disabled repository features without generating warnings.

#### <mark style="background-color:blue;">Incorrect default branch and resource count in summary after restoring a repository to local device</mark>

Restored repositories now have the correct default branch and show accurate **LFS** file counts.

#### <mark style="background-color:blue;">GitLab — closed milestone recreates as open</mark>

Closed milestones are now restored with their correct **closed** status.

***

<p align="center"><a href="https://gitprotect.io/latest-update.html#changelogs">ALL GITPROTECT SOFTWARE RELEASES</a></p>