Skip to content

Jira data restores & managing issue statuses

Jira JQL

Courtesy - iDalko

Introduction

When it comes to managing software development projects, Jira is one of the most popular tools. It is often used not only in software development but also for service management and work management to assign tasks, log work, track progress and manage issues. 

One of the most important aspects of using Jira is setting the correct status for each issue. In a Jira project, the "status" of an issue is an important field that provides information about the current state of that issue. This is important because it helps team members and stakeholders understand what has been done and what needs to be done to resolve the issue.

Understanding the Basics of Managing Issue Statuses

Setting the correct status is important because it allows team members to quickly and easily see the progress of an issue. For example, an issue with the status of "To Do" indicates that it has not yet been started, while an issue with the status of "In Progress" indicates that work is currently being done on it. This helps team members prioritize their work and it can help to prevent tasks from slipping through the cracks. It also helps to provide clarity as to what tasks are pending or completed. 

Under unexpected circumstances, where several issues can be bulk updated incorrectly or issues can be deleted, you may decide to recover the deleted issues or update the issues to previous state from a backup copy.

Restoring & Recovering Issue Statuses

Using the Revyz backup & restore app for Atlassian Jira, you will be able to restore the deleted issues or revert back the existing issues. However, Atlassian APIs have limitations wherein it doesn't allow API users to set the status directly once the issue is reverted/created. As per Atlassian - Status can be changed i.e. issue can be transitioned only as per the 'Workflow' transitions defined by the customers. If the current Status of issue before reverting has no direct transition between the target status then API users won't be able to transition the issue without prior knowledge of every workflow. This is a known limitation for all vendors using API.

Example: In the following workflow, any issue in 'Waiting Review' status cannot be transitioned directly into 'Closed' status. The transition journey would look like this 'Waiting review' -> 'Draft' -> ' Code review' -> 'Closed'. Additionally, there is complexity of validations and post functions which can break the entire transition which can break automated transition via API if validation rules are not met.

Here’s how the status transition would look like in the above example.

1 - 

Workflow - 1

2 - 

Workflow - 2

3 - 

Workflow-5

Actual workflow which complicates the automated transition via APIs

Workflow - 3

 

To address this Atlassian API limitation, here at Revyz we recently launched a new feature. Inline with Revyz’s vision of providing truly enterprise grade features, the new feature provides you more granular visibility into what is happening and enables you to take actions by yourself:

1 - Now under ‘Job details’, you can see if status is not set correctly for any restored issue. If the status is not correct it is marked with ‘05002’ status_code. 


Restore - 1

2 - Once the restore is done, you will be able to go to the ‘Post actions’ section under Job details and then download the JQL csv. This JQL csv contains a list of JQLs which lists all the restored issues and its respective target statuses which should have been restored.

Post Actions

Contents of downloaded JQL csv file:

Post Actions CSV

3 - The final step is to run the given JQL in Jira advanced search and transition all the issues using Jira's ‘Bulk update’ feature.

  • JQL-1
  • JQL-2
  • JQL-3
  • JQL-4
  • JQL-5

Repeat this process till the issue is transitioned into the desired status.

Conclusion

In summary, setting the correct status for each Jira issue is important because it helps to ensure that tasks are completed on time and to the right quality standards and it helps to identify issues that need immediate attention. With Revyz you can just do that with ease!

How can Revyz Help

Implementing a data protection strategy for Atlassian Jira cloud has become a necessity and equally complex. With limited native options from Atlassian, you will have to either build some custom scripts, manage data on your own to address your data protection needs or you leverage 3rd party SaaS applications such as Revyz to offload data protection from your core IT team.

Revyz Backup & Restore app for Jira can store data securely & remotely, making it available for various recovery scenarios without having you to rollback the entire site.

Try Revyz for free - Atlassian marketplace link.  Share your feedback on how we can improve & what other use cases you would want Revyz to address.

Blogs from Revyz

Jira Backup Requirements

Atlassian Data Protection - Challenges in the cloud

7 Reasons Why A Jira Backup & Restore Solution Is A Must Have

Pro's and Con's of using Jira Cloud Database Backup & Restore

Mystery of Incorrect Sprint Reports

Jira - Restoring Issue Family Hierarchy

SaaS Backup: An Antidote to Ransomware

Data Backup - A Key Pillar of Insider Risk Management

What’s your Atlassian Cloud Migration & Data Protection Strategy?

A Guide to SaaS Shared Responsibility Model

Why you need a SaaS backup strategy and solution

Why we built Revyz

Blog comments