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)

Best Practices

In this, the final chapter, we will focus on a number of best practices that you should always keep in mind when using Jira. You must have already realized that Jira is quite a flexible tool when it comes to customizing it, based on your requirements. At the same time, it is very important that configuration changes in Jira are done carefully from the outset and that you are aware of the consequences if these customizations are not performed correctly. Observing best practices will ensure the longevity and top-notch performance of your Jira instance.

Topics covered in this chapter include the following:

  • Setting up a change control board
  • Documenting your configurations
  • Not creating too many statuses
  • Not creating lots of custom fields
  • Using contexts
  • Using project roles over groups
  • Not modifying default configurations
  • Jira customization process