Book Image

Jira 8 Essentials - Sixth Edition

By : Patrick Li
Book Image

Jira 8 Essentials - Sixth Edition

By: Patrick Li

Overview of this book

This new and improved sixth edition comes with the latest Jira 8.21 Data Center offerings, with enhanced features such as clustering, advanced roadmaps, custom field optimization, and tools to track and manage tasks for your projects. This comprehensive guide to Jira 8.20.x LTS version provides updated content on project tracking, issue and field management, workflows, Jira Service Management, and security. The book begins by showing you how to plan and set up a new Jira instance from scratch before getting you acquainted with key features such as emails, workflows, and business processes. You’ll also get to grips with Jira’s data hierarchy and design and work with projects. Since Jira is used for issue management, this book will help you understand the different issues that can arise in your projects. As you advance, you’ll create new screens from scratch and customize them to suit your requirements. Workflows, business processes, and guides on setting up incoming and outgoing mail servers will be covered alongside Jira’s security model and Jira Service Management. Toward the end, you’ll learn how Jira capabilities are extended with third-party apps from Atlassian marketplace. By the end of this Jira book, you’ll have understood core components and functionalities of Jira and be able to implement them in business projects with ease.
Table of Contents (18 chapters)
Part 1: Introduction to Jira
Part 2: Jira in Action
Part 3: Advanced Jira

Field configuration

As you have already seen, fields are used to capture and display data in Jira. Fields can also have behaviors, which are defined by field configuration. For each field in Jira, you can configure the behaviors listed here:

  • Field description: This is the description text that appears under the field when an issue is edited. With field configuration, you can have different description text for different projects and issue types.
  • Visibility: This determines whether a field should be visible or hidden.
  • Required: This specifies whether a field will be optional or required to have a value when an issue is being created/updated. When applied to select, checkbox, or radio button custom fields, this will remove the None option from the list.
  • Rendering: This specifies how the content is to be displayed and what the field looks like when you are editing it. For example, a text-based field can have a default text editor, which will be a simple text-based...