Last Updated on February 27, 2025

Jira Assets Backup & Restore – now with GitProtect

We got it! We are proud to announce that GitProtect 1.9.5 now supports fast and reliable Jira Assets backup and recovery – with both Granular Restore and Disaster Recovery! As a result, our portfolio of protected DevOps data has expanded to include another important resource for our customers – and we continue to maintain our mission to protect the largest scope of DevOps platforms in the world.

What’s more, from the first release you got the most comprehensive way to protect your Assets and Jira Service Management. Now you can backup and restore the following data associated with your organization.

Global elements:

  • Schema
  • Roles
  • Icons
  • Reference types
  • Statuses
  • Object types
  • Attributes
  • Objects

To start protecting Jira Assets select them during the setup of a backup plan in the Additional data section – the feature is disabled by default. 

Now what interests you the most – to provide you with the highest security standards GitProtect brings both Granular Restore of only chosen items and Disaster Recovery to protect your Assets in every possible scenario. And now, wait for it…

…we are the only vendor that allows you to restore Assets with original objects’ IDs

Hard to believe? Check it yourself!

Granular restore of Assets allows to restore:

  • selected schemas (along with object types and objects themselves),
  • selected object types (along with objects),
  • selected objects.

Quick note:  Jira Assets backup and restore do not require any additional GitProtect license. If you already are protecting Jira data you are covered. 

Try GitProtect for Jira Assets

GitProtect Backup for Jira is a Forge app now

Yes, GitProtect for Jira in the Atlassian Marketplace is now a Forge application. What does it mean? From now on you can install and run our solution even more natively in your Jira to perform backup and restore. In just a few clicks. 

And if you need more advanced features, such as replication, assigning additional storage, or managing administrators, you have access at your fingertips – literally with one click.

If you have already installed our app from Atlassian Marketplace, Atlassian is undergoing an automatic update to the Forge version. 

Check our new Forge App

New bypass for vendor push limitations

Before starting the restore process, GitProtect verifies the size of the selected repositories. If it detects that one of the selected repos exceeds 2 GB user is noted to proceed with the restore in a manual mode. This is the recommended option, because due to the vendor limitation automatic process is blocked. 

Go to the app now

Azure DevOps root account excluded from a backup task

Wherever you are a new user or expanding data protection to Azure DevOps, you probably already discovered that GitProtect throttling prevention is a great feature. Sometimes, however, the person who sets up the account does not manage it on a regular basis or leaves the company. For such scenarios, we have made it possible to exclude the main account from the backup process. This authorization data will not be used in the given task, and thus we will not use the API limits of the specified user. Note: you would have to provide us with another authorization method in such a scenario. 

GitProtect Backup for Azure DevOps

List of other changes and improvements: 

  • GitHubApp is now authorized with the Installation Token
  • Faster GitLab backup and restore after deploying a new optimizations package
  • Extended information about lack of permission in backup errors and warnings 
  • Forever Incremental scheme disabled for Jira copies for better and faster performance

Comments are closed.

You may also like