Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
JIRA 7 Essentials - Fourth Edition

You're reading from  JIRA 7 Essentials - Fourth Edition

Product type Book
Published in Nov 2016
Publisher Packt
ISBN-13 9781786462510
Pages 398 pages
Edition 4th Edition
Languages
Author (1):
Patrick Li Patrick Li
Profile icon Patrick Li

Table of Contents (17) Chapters

JIRA 7 Essentials - Fourth Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
1. Getting Started with JIRA 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

Built-in fields


JIRA comes with a number of built-in fields. You have already seen a few of them in the previous chapters. Fields such as summary, priority, and assignee are all built-in. They make up the backbone of an issue, and you cannot remove them from the system. For this reason, they are referred to as system fields.

The following table lists the most important built-in fields in JIRA:

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 $15.99/month. Cancel anytime}

System field

Description

Assignee

This specifies the user who is currently assigned to work on the issue.

Summary

This specifies a one-line summary of the issue.

Description

This provides a detailed description of the issue.

Reporter

This specifies the user who has reported this issue (although most of the time it is also the person who has created the issue, but not always).

Component/s

This specifies the project components the issue belongs to.

Effects Version/s

This specifies the versions the issue effects are found in.

Fix Version/s

This specifies the versions the issue will be...