Book Image

Jira 8 Administration Cookbook - Third Edition

By : Patrick Li
Book Image

Jira 8 Administration Cookbook - Third Edition

By: Patrick Li

Overview of this book

Jira is a project management tool used widely by organizations to plan, track, and release software. Jira administrators are at the heart of these processes and need to know how to successfully administer and customize Jira offerings. This updated Jira 8 Administration Cookbook demonstrates how to efficiently work with Jira Core and Jira Service Desk. The book starts with a variety of recipes to help you manage users and workflows. You'll learn how to set up custom forms and capture important data with custom fields and screens. Next, you'll gain insights into the latest email capabilities, which will assist you with everything from managing outgoing email rules to processing incoming emails for automated issue creation. Later, you'll be guided through running scripts to automate tasks, getting easy access to logs, and even working with tools to troubleshoot problems. The book will also ensure you understand how to integrate Jira with Slack, set up SSO with Google, and delegate administrator permissions. Finally, a dedicated section on Jira Service Desk will enable you to set up and customize your own support portal, work with internal teams to solve problems, and achieve optimized services with Service Level Agreement (SLA). By the end of this book, you'll have the skills you need to extend and customize your Jira implementation effectively.
Table of Contents (11 chapters)

Copying configuration settings between Jira instances

If you have a controlled IT environment where changes need to go through development, testing/staging, and production processes, then, without a doubt, you will know how painful it is to promote Jira configuration changes across different environments. Since Jira does not provide a way to export configurations out of the box, all changes will need to be manually applied to each environment, which is both time-consuming and error-prone.

In this recipe, we will look at using a specialized tool that can help to make this process easier.

Getting ready

How to do it...

The Configuration Manager for Jira add-on requires you to first create a snapshot. A snapshot contains all the configuration settings you want to copy over to a different Jira instance.

You can create two types of snapshot:

  • System: This includes all configurations in Jira.
  • Project: This includes only configurations required for the selected project.

Proceed with the following steps to create a configuration snapshot:

  1. Navigate to Administration > Configuration Management > Snapshots.
  2. Click on the Add Snapshot button.
  3. Opt to create either a System Configuration or Project Configuration snapshot.
  4. Enter a name for the snapshot.
  5. Click on the Create button. The following screenshot shows the details of the snapshot we created:

Having created the snapshot, there are several ways in which we can promote and deploy changes to another Jira instance. We can either download the snapshot ZIP file and upload it or link the two Jira instances together with Application Link and load the snapshot remotely. We will use the snapshot file option in this recipe. Proceed with the following steps to deploy a snapshot:

  1. Log in to the other Jira instance as an administrator.
  2. Navigate to Administration > Configuration Management > Deploy.
  3. Select the From Snapshot File option.
  4. Choose the snapshot ZIP file.
  5. Click on the Deploy link to start the deployment.

The add-on will walk you through a deployment wizard, where it will analyze the contents of the snapshot and determine whether your current Jira system meets all the necessary requirements. For example, in the following screenshot, it has informed us that there is an add-on version mismatch:

After the add-on has determined that all the requirements are met, it will provide a quick summary of all the changes that will be applied (seen in the following screenshot). This is a good time to review the list of items to make sure we are not introducing unwanted changes accidentally, as shown in the following screenshot:

If everything looks good, we can finish migrating the configuration changes and deploy them to the target instance.