custom field not visible on screen

[anthony.ng]

I've created a custom fiels called TX-PMO-project-code and added it to a screen called TX-PMO-default screen. This field is not visible in work items, my other custom fields do appear. 

[Hans Polder _Devoteam_]

Hi Anthony,

Most commonly, this issue would be caused by the custom field not having the right context. It's possible to add a custom field to the screen, but if the custom field is configured to be used in specific projects only, then it won't show on your work item. 

Can you share some screenshots of the configuration of your custom field, and more specifically its contexts? 

If you need help on how to identify that, please let me know, and I'll gladly provide you the steps.

[anthony.ng]

Hi Hans, thanks for replying. This is te configuration of the custom field:

[Hans Polder _Devoteam_]

Hi @anthony.ng ,

I see the problem :) As I mentioned, issues like this are 99/100 times caused by the context configuration. In the screenshot you provided, I can see that the field is only configured to show for Epics.

In the screenshot you shared in your original post, you were showing TPPTN-7, which is a Story. If you test it on TPPTN-6 (the epic), you should see the field there without issues.

To solve this, you can do one of two things:

1) In the last screenshot you shared, click 'Edit configuration' en add the Story work type to the context.

2) My advice: In the last screenshot you shared, click 'Edit configuration' en remove the restriction for Epic (so that the field will show for all work types). Generally, you should try to refrain from limiting field visibility for work types, as you'll always run into these kind of issues in the future (long after you've forgotten that you configured it this way). 

If you need any detailed advice on how to approach this, please let me know. Also, if you want to discuss how to approach your specific use case, please share more details so I can think along and suggest a solution if needed :)

[anthony.ng]

Thanks I tried it, it works but now I have two option lists. I'll investigate further.. 

[Hans Polder _Devoteam_]

Hi Anthony,

Sorry for the late response - I missed your reply here. 

Can you share if you got it to work? If not, can you share some screenshots on what you're observing, with the 'two option lists' issue? Please share a screenshot of your custom field context configuration as well. 

Thanks!

Hans