Book Image

Jira 8 Essentials - Sixth Edition

By : Patrick Li
5 (1)
Book Image

Jira 8 Essentials - Sixth Edition

5 (1)
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)
1
Part 1: Introduction to Jira
4
Part 2: Jira in Action
9
Part 3: Advanced Jira

Understanding issues

An issue in Jira usually represents a unit of work that users will work on. Depending on how you are using Jira, an issue can also represent other things and concepts in the real world. For example, in a software development project, an issue can be a bug or a story, while in an IT service project, an issue can be an incident or a support request.

Despite all the differences in what an issue can represent, there are several key aspects that are common to all issues in Jira, listed as follows:

  • An issue must belong to a project.
  • It must have a type, also known as an issue type, which indicates what the issue represents.
  • It must have a summary. The summary acts like a one-line description of what the issue is about.
  • It must have a status. A status indicates where along the workflow the issue is at a given time. We will discuss workflows in Chapter 7, Workflow and Business Process.

In summary, an issue in Jira represents a unit of work...