Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Will Setting Custom Field Context to A Specific Project Limit It Show On Others Projects?

Dan Koh April 3, 2025

While working on this questionnaires and I came across Question 3.2.7. The correct answer shown is B, even Chatgpt said it's B. I tested in my JIRA instance but it don't work as what the answer mentioned.  Here's how I test:-

1. Created Project A and Project B, both shared all same configuration schemes included screen schemes.
2. Create a new custom field called "Test Custom Field" with Context set to Project A only
3. Access to Project A screen configuration scheme, update all screens to consist "Test Custom Field"
4. Test create new ticket in Project A verified custom field showing
5. Test create new ticket in Project B, it's STILL showing... :( Hmmmm... Is it a bug? or am I doing something wrong? or I had wrong understanding with with questions?

 

ACP-100 Jira Admin for DC sample questions : Atlassian

 

Question 3.2.7 Two projects share all of their schemes. Users see a particular custom field when editing issues in one of the projects, but not the other. Which configuration is responsible for the difference? Options:-

A. field configuration
B. custom field context
C. screen
D. permission scheme
E. issue security scheme

Thanks for your help :) 

1 answer

1 accepted

3 votes
Answer accepted
Dan Koh April 3, 2025

After spending 5-10 min typing it here & I went back to refresh and create new ticket, it's working as expected now :) Mysteries resolved, it's cache/indexing issue.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
9.12.12
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events