Book Image

Jira Quick Start Guide

By : Ravi Sagar
Book Image

Jira Quick Start Guide

By: Ravi Sagar

Overview of this book

Jira is an issue tracker and project management system. With their latest release, the Jira team has now expanded their user base to agile teams as well as business teams. This book provides a comprehensive explanation covering all major components of Jira, including Jira Software, Jira Core, and Jira Service Desk. This book starts with an introduction to Jira's unique features and how it can be used as an issue-tracking tool. It will then teach you about how a new project is created by a Jira administrator, what responsibilities there are, and using correct and relevant schemes in your project. You will then learn how to configure project workflows and fields for project screens. You will understand the various permissions used in projects and the importance of project roles in Jira. Then, the book talks about the concepts of versions acting as milestones and using components when handling issues in your projects. It will then focus on analysing data using built-in reports and creating dashboards in Jira. At the end, it will discuss various best practices for users as well as project managers or project administrators.
Table of Contents (10 chapters)

Not creating too many statuses

Workflows are one of the main aspects of Jira customizations. They define the life cycle of an issue as it goes through different stages. A workflow has a variety of statuses, and various transitions between them. Sometimes, when a new workflow is created, there might be a requirement to create a new status. Now, before creating a new status, please go through the existing list of statues in your instance and check whether any of those existing statuses can be reused.

Reusing a status is only possible when their names are a bit generic and not overly project-specific. For example, Awaiting feedback and Feedback awaited are more or less the same, and there is no need to create a status such as Feedback 123.

Statuses are created globally and Jira workflows can use them, which is why you should not try to create too many statuses.