Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering JIRA 7

You're reading from   Mastering JIRA 7 Become an expert at using JIRA 7 through this one-stop guide!

Arrow left icon
Product type Paperback
Published in Oct 2016
Publisher Packt
ISBN-13 9781786466860
Length 450 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Ravi Sagar Ravi Sagar
Author Profile Icon Ravi Sagar
Ravi Sagar
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Planning Your JIRA Installation 2. Searching in JIRA FREE CHAPTER 3. Reporting – Using Charts to Visualize the Data 4. Customizing JIRA for Test Management 5. Understanding Zephyr and its Features 6. Sample Implementation of Use Cases 7. User Management, Groups, and Project Roles 8. Configuring JIRA User Directories to Connect with LDAP, Crowd, and JIRA User Server 9. JIRA Add-On Development and Leveraging the REST API 10. Importing and Exporting Data in JIRA and Migrating Configuration 11. Working with Agile Boards in JIRA Software 12. JIRA Administration with ScriptRunner and the CLI Add-on 13. Database Access 14. Customizing Look, Feel, and Behavior 15. Implementing JIRA Service Desk 16. Integrating JIRA with Common Atlassian Applications and Other Tools 17. JIRA Best Practices 18. Troubleshooting JIRA

Using project context to assign different options in multiple projects

Let's say we have a custom field called Customer. This is a select list with different values, which users can select while creating an issue. If JIRA is used by multiple teams, each working on a different project, it's quite possible that the customer list will be different. One project may cater to a different set of customers than others. One approach to deal with this situation is to enter all the customers in a single list, but this will lead to confusion among the team members who raise the tickets and it will also lead to errors, because users might select the wrong customers.

A different custom field can be created for each project to deal with this problem (each having its own list of customers), but this leads to redundancy, as we would store the same type of information in each list.

JIRA's custom fields offer a solution to this problem using context. Perform these steps to create a new context...

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
Banner background image