Book Image

JIRA 7 Essentials - Fourth Edition

By : Patrick Li
Book Image

JIRA 7 Essentials - Fourth Edition

By: Patrick Li

Overview of this book

Atlassian JIRA is an enterprise-issue tracker system. One of its key strengths is its ability to adapt to the needs of the organization, ranging from building Atlassian application interfaces to providing a platform for add-ons to extend JIRA's capabilities. JIRA 7 Essentials, now in its fourth edition, provides a comprehensive explanation covering all major components of JIRA 7, which includes JIRA Software, JIRA Core, and JIRA Service Works. The book starts by explaining how to plan and set up a new JIRA 7 instance from scratch for production use before moving on to the more key features such as e-mails, workflows, business processes, and so on. Then you will understand JIRA's data hierarchy and how to design and work with projects in JIRA. Issues being the corner stone of using JIRA, you will gain a deep understanding of issues and their purpose. Then you will be introduced to fields and how to use custom fields for more effective data collections. You will then learn to create new screens from scratch and customize it to suit your needs. The book then covers workflows and business processes, and you will also be able to set up both incoming and outgoing mail servers to work with e-mails. Towards the end, we explain JIRA's security model and introduce you to one of JIRA’s new add-ons: JIRA Service Desk, which allows you to run JIRA as a computer support portal.
Table of Contents (17 chapters)
JIRA 7 Essentials - Fourth Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

The HR project


In the previous chapters, you configured your JIRA to capture data with customized screens and fields, and processed the captured data through workflows. What you need to do now is secure the data you have gathered to make sure that only the authorized users can access and manipulate issues.

Since your HR project is used by the internal team, what you really need to do is put enough permission around your issues to ensure that the data they hold does not get modified by other users, by mistake. This allows us to mitigate human errors by handling access accordingly.

To achieve this, you need to have the following requirements:

  • You should be able to tell who belongs to the HR team

  • Restrict issue assign operations to only the user that has submitted the ticket and members of the HR team

  • Do not allow issues to be moved to other projects

  • Limit the assignee of tickets to the reporter and members of the HR team

Of course, there are a lot of other permissions we can apply here; the preceding...