Last Updated on September 10, 2024

Jira is a project management tool that helps IT teams simplify their DevOps and PM processes. Also, it supports easy collaboration throughout the team, thanks to the complex issue-tracking system. 

However, one thing you should be cautious of… It is the accidental or intentional deletion of important issues. Why? The loss of even a piece of project data can have devastating consequences and throw your team a few steps back… What measures should be taken to minimize or even eliminate the consequences of the Jira data deletion? Let’s talk about it in this article…

Why should you back up your Jira data? 

To start with, what about looking at the following scenario? Let’s say your team uses a backup script to protect Jira data, but unfortunately for you, the script overwrites your backed-up Jira data. Thus, if some of your issues are accidentally deleted and you haven’t noticed it on time before another backup, your data will be lost. So, human errors, outages, and ransomware attacks are among the reasons for protecting your Jira issues and other Jira data.

Another reason is the Shared Responsibility. Let’s not forget – the user is responsible for its account’s data within the Atlassian Cloud Security Shared Responsibility Model. What about the provider’s duties? It is responsible for the security of its service and infrastructure.

One more aspect, that’s worth our attention is security compliance. If your organization is about to pass and comply with security protocols, like GDPR, SOC 2, HIPAA, or ISO 27001, then backup and Disaster Recovery strategy is a necessary measure. 

Are there any options to restore a deleted Jira issue?

Atlassian supplies its users with manual exports and imports but it doesn’t provide granular restore. It also has a complete backup on infrastructure-level, not supporting single account backup. In both sitations, in case of accidental deletion of an issue(s), you will not be able to restore it. Once deleted issue is gone forever. But does it have to be that way?

To cover this challenge with a single Jira issue restore, you can use a third-party backup and Disaster Recovery solution that permits granular restore of only specified data. Hence, for example, you will be able to restore only the necessary issue with all its data, including configurations, comments, attachments, links, tasks, and sub-tasks.

Step-by-step guide on restoring Jira issues with GitProtect.io

Once you start backing up your Jira environment with GitProtect backup and Disaster Recovery software, you can easily restore only a single piece of your Jira data. So, let’s look at an example, go through the Jira issues restoration steps, and recover our deleted Jira data:

First, open your GitProtect.io interface and click DevOps on the left side of your screen. Then, choose Jira and press the Restore button on the right side of your screen.

Jira issue restore with GitProtect 1

In an opened window, you will need to select the needed backup plan and press the Restore button. Once you click it, you will see two possible options – Disaster Recovery and Granular Restore. Our option is Granular Restore. So, click it.

Jira issue restore with GitProtect 2

You will see a new window with the Restore Destination options, including Original organization (your Jira account), New organization, and Device (On-Prem). In our case, we want to restore the deleted issue to our existing Jira account. So, pick Original organization up and press Next

Jira issue restore with GitProtect 3

The next step is to choose what data you need to restore – projects, issues, attachments, or workflows. In our case, we have a deleted issue, so let’s choose the Restore Issue option and click the Next button. 

Jira issue restore with GitProtect 4

As all your issues are related to different projects, with the next step, you will need to select which project contained the delete issue. So, once you see the needed project click Configure and Select individual – don’t forget we want to restore a single deleted issue. If you want to restore all the issues in the project, you will need to opt for Select all

Jira issue restore with GitProtect 5

After you define a project, you will see the list of issues of that project. All you need to do is to find a deleted issue. To make the process easier,  you can use a search bar and look for the needed issue by key, issue type, or its name.

Jira issue restore with GitProtect 6

Once you find a necessary issue or issues, click Proceed.

Jira issue restore with GitProtect 7

Then, you will get back to the project window where you can check if you picked up the correct project or projects. If everything is correct, just click the Proceed button. 

Jira issue restore with GitProtect 8

Then, your task is to configure the mapping by clicking Edit. It will give you the possibility to map your restored issue to the existing issue or an absolutely different one. At this stage, you can also define whether you want to restore attachments and/or child issues. As an option, you can also force to restore your issue as a new one.

Jira issue restore with GitProtect 9

In the Configure Mapping window, you need to pick up the place to map your issue. Then, click Apply.

Jira issue restore with GitProtect 10

Finally, once the relevant options are set, press Start now. And voilá, your Jira deleted issue or issues are being restored!

Jira issue restore with GitProtect 11

Takeaway

Jira backup is an important part of the security strategy. And issues are not the only data you need to protect. Imagine, what if something goes wrong with your entire project? What if the project data is lost? Catastrophe… That’s why, your Jira backup strategy should include all the Jira account data. Thus, you will always be sure that your critical Jira data is accessible and recoverable to guarantee business continuity in project management. 

[FREE TRIAL] Ensure compliant DevOps backup and recovery with a 14-day trial🚀

[CUSTOM DEMO] Let’s talk about how backup & DR software for DevOps can help you mitigate the risks

Comments are closed.

You may also like