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

Preparing the JIRA configuration document

The configuration document should have information about all the schemes, along with the relevant background information to justify it.

This document should have the following sections.

What kind of issue tracking needs to be done?

First, start by asking these questions: what kind of issue tracking is required in JIRA? Do you want to keep track of your customer complaints or track bugs in your ongoing project? You may be tempted to start using JIRA and customize it on-the-go, but this approach will lead to a messed-up system in the long run and will be difficult to manage.

Issue types required

Once the purpose of using JIRA is clear, identify what kinds of issue need to be tracked. If JIRA is going to be used for simple bug tracking, then the existing issue types are sufficient, but if you want to use JIRA for support tickets, then you might want to create new issue types.

Best practices

Create new issue types only when existing ones cannot be used. Always...