Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
JIRA 7 Essentials

You're reading from   JIRA 7 Essentials Explore the great features of the all-new JIRA 7 to manage projects and effectively handle bugs and software issues

Arrow left icon
Product type Paperback
Published in Nov 2016
Publisher Packt
ISBN-13 9781786462510
Length 398 pages
Edition 4th Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Patrick Li Patrick Li
Author Profile Icon Patrick Li
Patrick Li
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Getting Started with JIRA FREE CHAPTER 2. Using JIRA for Business Projects 3. Using JIRA for Agile Projects 4. Issue Management 5. Field Management 6. Screen Management 7. Workflow and Business Process 8. E-mails and Notifications 9. Securing JIRA 10. Searching, Reporting, and Analysis 11. JIRA Service Desk

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime