Book Image

Mastering JIRA

By : Ravi Sagar
Book Image

Mastering JIRA

By: Ravi Sagar

Overview of this book

<p>JIRA is an issue-tracking tool from Atlassian and has gained immense popularity in recent years due to its ease of use and, at the same time, its customization abilities and finely grained control over various functions. JIRA offers functionalities for creating tasks and assigning them to users and many useful add-ons can be added such as JIRA Agile for Agile tracking and Groovy scripts, a powerful tool for administering customizations for customizations.</p> <p>This book explains how to master the key functionalities of JIRA and its customizations and add-ons, and is packed with real-world examples and use cases. You will first learn how to plan JIRA installation. Next, you will be given a brief refresher of fundamental concepts and learn about customizations in detail. Next, this book will take you through add-on development to extend JIRA functionality. Finally, this book will explore best practices and troubleshooting, to help you find out what went wrong and how to fix it.</p>
Table of Contents (23 chapters)
Mastering JIRA
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

The Project Import utility


The Restore System procedure is performed when the complete instance has to be restored or moved to another server, but there can be a scenario when you just need to restore a single project from another JIRA instance.

Let's take an example of a company that has multiple JIRA instances used by various other business units. These business units work independently of each other; they have different teams and work from different geographic locations. As you know, these days companies do reorganization quite often. Due to this reorganization process, a few projects from one business unit need to be transferred to another business unit. All the project code and documents along with the projects need to be transferred as well.

In this case, we cannot simply take a backup of one instance and restore it in another because it will wipe out the data in the target instance. The restore process has to be done only for a few selected projects.

Atlassian understood this scenario...