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
Credits
About the Author
Acknowledgements
About the Reviewer
www.PacktPub.com
Preface

Using project context to assign different options in multiple projects


Let's say we have a custom field called Customer. This is a select list with different values, which users can select while creating an issue. If JIRA is used by multiple teams, each working on a different project, it's quite possible that the customer list will be different. One project may cater to a different set of customers than others. One approach to deal with this situation is to enter all the customers in a single list, but this will lead to confusion among the team members who raise the tickets and it will also lead to errors, because users might select the wrong customers.

A different custom field can be created for each project to deal with this problem (each having its own list of customers), but this leads to redundancy, as we would store the same type of information in each list.

JIRA's custom fields offer a solution to this problem using context. Perform these steps to create a new context:

  1. Go to Administration...