Book Image

Mastering JIRA 7 - Second Edition

By : Ravi Sagar
Book Image

Mastering JIRA 7 - Second Edition

By: Ravi Sagar

Overview of this book

Atlassian JIRA 7 is an enterprise issue tracker system. One of its key strengths is its ability to adapt to the needs of an organization, ranging from building software products to managing your support issues. This book provides a comprehensive explanation covering all three components of JIRA 7, such as JIRA Software, JIRA Core, and Jira Service Desk. It shows you how to master the key functionalities of JIRA and its customizations and useful add-ons, and is packed with real-world examples and use cases. You will first learn how to plan for a JIRA 7 installation and fetch data. We cover JIRA reports in detail, which will help you analyze your data effectively. You can add additional features to your JIRA application by choosing one of the already built-in add-ons or building a new one to suit your needs. Then you'll find out about implementing Agile methodologies in JIRA by creating Scrum and Kanban boards. We'll teach you how to integrate your JIRA Application with other tools such as Confluence, SVN, Git, and more, which will help you extend your application. Finally, we'll explore best practices and troubleshooting techniques to help you find out what went wrong and understand how to fix it.
Table of Contents (25 chapters)
Mastering JIRA 7 - Second Edition
About the Author
About the Reviewer

Setting up JIRA for requirement management

Let's take a look at the configuration for using JIRA requirement management; we will store issues that are related to requirements. This will also ensure that expectations of the project are captured and later verified during testing.

Issue types

The following table lists the different issue types for requirement management:

Scheme name

Issue types


Requirements—Issue Type Scheme



Change Request



New Feature

New User Request


Create the issue types that are not available


We will use a custom workflow for the Requirements issue type; it will be used to store the project requirements; for the rest of the issue types, the default JIRA workflow will be used.

The following table depicts the requirements workflow:





In Progress

A new issue can be moved to the In Progress state when the work starts

In Progress



  • Condition: Only the assignee...