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

Working with project roles

Every project is executed by different people, each with their own set of responsibilities. Usually, certain aspects of the project are taken care of by these people who are part of a team. For instance, in the case of a software project, there will be a project lead who manages everything in the project and is responsible for overall progress, developers who work on the features, and then there is a team of testers to verify the built features. The first versions of JIRA had only groups, and JIRA administrators would end up creating multiple groups for various projects, such as proj-administrators, proj-developers, and so on. At the same time, the permission scheme for each project also needed to be defined for these groups. JIRA developers realized this was a problem and introduced the concept of project role that allows not only JIRA administrators but also the project administrator to add and remove users to their project roles.

In JIRA, you could have roles...