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 bug tracking

JIRA can be used out-of-the-box for bug tracking. It comes with a default issue type called Bug, along with other issue types. However, you may be required to make certain changes in the default configurations in the future, and it is a good idea to create custom schemes even for bug tracking. Of course, we will copy the default schemes and make changes in the copied configurations.

Issue types

The following are the issue types for bug tracking:

Scheme name

Issue types


Default Issue Type Scheme



New Feature

New User Request


There's no need to create new issue types or new schemes here


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

The following is the workflow for bug tracking:








Waiting for Client

  • Condition: Only the assignee can...