We’ve done it — Jira Granular Backup is now live in GitProtect! And that’s not all. The GitProtect 2.1.0 release also introduces backup & restore for Azure DevOps Artifacts, expands protection coverage for GitHub Projects by draft issues, and brings a whole set of improvements across the platform. Let’s break down what’s new and why it matters for DevOps and Jira Admins.

Jira Granular backup is here

You asked — we delivered. With Jira Granular Backup, you can now protect exactly what your team needs, with full control over what to back up, how often, and at what level of detail. This update gives you precision, flexibility, and performance-aware protection for your Jira Cloud with different levels of granularity:

  • Space-level, which allows you to protect all spaces or hand-pick only the ones you need. You can even define rules to automatically include spaces based on name, key, or type in your backups.
  • Work-item-level, on which you can choose which work items to include in the backup in the selected spaces — such as Roles, Versions, Components, Boards, Notification Schemes, Issues, Assets, and Automation Rules.

Moreover, on the work-item level, you can back up exactly the items that matter most, using JQL filters. By simply defining a JQL query in your Jira Cloud and providing it to GitProtect’s backup configuration, you can easily exclude some items, like Attachments, Comments, Fields, or Links, or just limit the number of protected items. It gives you complete control and flexibility over your Jira Cloud data protection — directly from Jira Cloud itself. 

🎙️ Join our upcoming webinar — Master Your Jira Cloud Backup Strategy with GitProtect’s Granular Backup — and see in practice how your organization can benefit from this powerful new feature in practice! 🚀

Get better RPO for critical Jira data

Being a supplement to Jira Disaster Recovery backup, Jira Granular backup helps organizations significantly improve their Recovery Point Objective (RPO). 

A Jira Disaster Recovery backup allows organizations to protect their entire Jira Cloud site and restore everything in the event of a failure. However, full-site backups can take a bit longer to run, which makes it difficult to meet strict RPO requirements on their own. That’s why many teams need an additional Granular Backup plan that focuses only on their most critical Jira spaces. These smaller, targeted backups can be performed much more frequently than a full DR backup. 

With Granular Backup for Jira Cloud, organizations can now protect what matters most — their mission-critical Jira spaces at higher frequencies and with far greater precision. 

In other words, with Granular Backup for Jira Cloud, organizations are able to control the maximum amount of data they can afford to lose in the event of a disruption. For example, if an RPO is 4 hours, it means that, in a worst-case scenario, the organization could lose no more than 4 hours’ worth of data without causing a serious business impact. 

By backing up critical spaces more often, Jira Granular Backup helps organizations meet strict security and compliance requirements, reduce potential data loss, and ensure stronger overall resilience.

Have site consolidation and site split made simple

Need to merge multiple Jira sites into one? The Jira Granular Backup feature can make it straightforward. Simply back up the selected spaces from multiple Jira sites and restore them into a new single target Jira site as new spaces. That’s it — your Jira Cloud site consolidation is complete.

Should you split a large site into several smaller ones? With GitProtect’s brand-new Granular backup for Jira Cloud, it’s easy. Back up only the Jira spaces your organization wants to move, and restore them to a new targeted Jira site(s). As easy as it’s said!

Merge Jira spaces to avoid operational complexity

With GitProtect’s newly released Jira Granular backup, you can merge work items from different spaces, even with different configs, workflows, and boards, into one single space. Thus, you will need no manual re-creation or cleanup.  

Safe configuration and change management

Spin up sandbox environments using disaster recovery backups, test major changes, and then, using Jira Granular backup, migrate only the updated items into the production site. It will help make all your processes controlled, predictable, and safe.

👉 Try Jira Granular Backup

Jira Disaster Recovery with the option to exclude attachments

Struggling to meet your Jira Disaster Recovery RPO because attachments slow everything down? With the GitProtect 2.1.0 release, you can now exclude attachments and run backups far more frequently — without sacrificing protection. Just split your Jira DR strategy into two plans:

  • a fast, frequent backup without attachments,
  • and a periodic full backup with everything included.

Azure DevOps Artifacts Backup and Restore

The GitProtect 2.1.0 update adds support for backing up and restoring Azure DevOps Artifacts — the central package hub your developers rely on for NuGet, npm, Maven, Python, and Universal Packages. 

So, you can now back up every feed and every package, down to its content. Moreover, GitProtect captures feeds permissions, views, and upstream sources, giving you airtight artifact supply-chain security and fast, reliable recovery when you need it most.

👉 Start protecting your Azure DevOps environment with GitProtect backup and DR

Extended support for GitHub Projects

The newest GitProtect release also brings extended support for GitHub Projects by draft issues and the most important fields from these issues, including status, labels, milestones, and custom fields.

Select repos within custom properties in GitHub backup

With GitProtect 2.1.0, you get a flexible and automated way to select GitHub repositories for a backup by creating a custom property in GitHub and using it in GitProtect while setting up a backup plan. What’s important, all repositories that have a selected custom property with the matching value will be automatically added to the backup copy. 

👉 Ensure reliable protection of your GitHub repositories and metadata with GitPortect backup and DR

The other improvements and fixes in GitProtect 2.1.0

  • Optimized restore of incremental Git repository backups and pull requests for GitHub Cloud organizations.
  • Improved option to select a target project when restoring Azure DevOps data.
  • Forced password change upon first login to the system.
  • and much more!

Read the complete GitProtect 2.1.0 changelog here.

Daria Kulikova, Content Writer at GitProtect.io
Daria is a Content Specialist at GitProtect.io, who has a degree in linguistics and an extensive translation background in different areas, including technology, IT, economics, etc. She loves self-improvement, so when she is offline, it’s easy to find her learning and expanding her knowledge in Cybersecurity, and DevSecOps.

Comments are closed.

You may also like