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)

Creating custom workflow transition logic

In previous recipes, we have looked at using workflow conditions, validators, and post functions that come out of the box with Jira and from other third-party apps.

In this recipe, we will take a look at how to use scripts to define our own validation rules for a workflow validator. We will address a common use case, which is to make a field required during a workflow transition only when another field is set to a certain value.

So, our validation logic will be as follows:

  • If the Resolution field is set to Done, the Solution Details field will be required.
  • If the Resolution field is set to a value other than Fixed, the Solution Details field will not be required.

Getting ready

For...