Forums

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

Field missing: Same Field Configuration, same screen scheme

Alexis Raptarchis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 24, 2020

Hi, 

 this is slowly driving me mad... Here is the situation:

  • Project A and Project B are sharing the same Field Configuration and the same Screen Scheme (neither of them is a "NextGen  Project").
  • On Project A the field "Story Points" is visible.
  • On Project B the field "Story Points" is not visible, even though it is configured under  "Issue Layout" on this Project. So the Project B is not oblivious to its existence.
  • Updating the field configuration as Admin to add a previously unassociated field to the shared screen schema works. E.g. the new field is visible in both projects.

Project A is the older project, for which the schemas were set up, if that makes a difference.


What am I missing here? 

Kind Regards,

Alexis

1 answer

1 accepted

2 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 25, 2020

If your projects have the same Field config scheme and Screen scheme, then the last reason a custom field such as Story points will go missing is that the field does not have a context for the project and/or issue type.

Go to admin -> issues -> custom fields and check for the contexts of story points.

Alexis Raptarchis
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 27, 2020

Thank you, that was it, the context for the project was missing. It is very confusing though that the custom field was listed in the "Configure Screen" of the affected project, even though the project context for that project was missing. 
 It really feels like there are way to many configuration matrixes affecting which fields are shown where tbh.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events