Book Image

Jira 8 Essentials - Sixth Edition

By : Patrick Li
Book Image

Jira 8 Essentials - Sixth Edition

By: Patrick Li

Overview of this book

This new and improved sixth edition comes with the latest Jira 8.21 Data Center offerings, with enhanced features such as clustering, advanced roadmaps, custom field optimization, and tools to track and manage tasks for your projects. This comprehensive guide to Jira 8.20.x LTS version provides updated content on project tracking, issue and field management, workflows, Jira Service Management, and security. The book begins by showing you how to plan and set up a new Jira instance from scratch before getting you acquainted with key features such as emails, workflows, and business processes. You’ll also get to grips with Jira’s data hierarchy and design and work with projects. Since Jira is used for issue management, this book will help you understand the different issues that can arise in your projects. As you advance, you’ll create new screens from scratch and customize them to suit your requirements. Workflows, business processes, and guides on setting up incoming and outgoing mail servers will be covered alongside Jira’s security model and Jira Service Management. Toward the end, you’ll learn how Jira capabilities are extended with third-party apps from Atlassian marketplace. By the end of this Jira book, you’ll have understood core components and functionalities of Jira and be able to implement them in business projects with ease.
Table of Contents (18 chapters)
Part 1: Introduction to Jira
Part 2: Jira in Action
Part 3: Advanced Jira

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 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 permissions 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 know 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 assignment of tickets to the reporter and members of the HR team

Of course, there are a lot of other permissions...