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

JIRA and screens


Before you can start working with screens, you need to first understand what they are and how they are used in JIRA.

Compared to a normal paper-based form, fields in JIRA are like the check-boxes and spaces that you have to fill in, and screens are like the form documents themselves. When fields are created in JIRA, they need to be added to screens in order to be presented to users. Therefore, you can say that screens are like groupings or containers for fields.

In most cases, screens need to be associated with issue operations through what are known as screen schemes. Screen schemes map screens to operations, such as creating, viewing, and editing issues, so that you can have different screens for different operations. Screen schemes are then associated with issue type screen schemes, which when applied to projects will map screen schemes to issue types. This lets each issue type in a project have its own set of screens. The only time when a screen will be used directly is...