Book Image

Mastering JIRA

By : Ravi Sagar
Book Image

Mastering JIRA

By: Ravi Sagar

Overview of this book

<p>JIRA is an issue-tracking tool from Atlassian and has gained immense popularity in recent years due to its ease of use and, at the same time, its customization abilities and finely grained control over various functions. JIRA offers functionalities for creating tasks and assigning them to users and many useful add-ons can be added such as JIRA Agile for Agile tracking and Groovy scripts, a powerful tool for administering customizations for customizations.</p> <p>This book explains how to master the key functionalities of JIRA and its customizations and add-ons, and is packed with real-world examples and use cases. You will first learn how to plan JIRA installation. Next, you will be given a brief refresher of fundamental concepts and learn about customizations in detail. Next, this book will take you through add-on development to extend JIRA functionality. Finally, this book will explore best practices and troubleshooting, to help you find out what went wrong and how to fix it.</p>
Table of Contents (23 chapters)
Mastering JIRA
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

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 this question, 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 kind of issues 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...