How can I associate custom fields with work types - company managed space

Question

I'm finding the online documentation to be inconsistent and confusing.  Not sure where to look anymore?

Piyu@Appcento · Answer

A field reaches a work type through three layers, screen, screen scheme, field configuration, and the field context is the one people forget to check. The screen decides where the field renders, the screen scheme decides which screen an issue type uses, the field configuration decides whether it is visible, required or hidden. The catch, if the field sits in a hidden field configuration or the screen is shared with other types, it looks like it never applied. Fastest debug path, open the issue and check the field configuration for it, then check the screen scheme for that issue type, then confirm the field's context covers that project and issue type. Wrong project scope on the field context is the most common reason it never renders.

Tomislav Tobijas · Answer

Hey @Allen Hirsch ,

On top of what the guys said, you'll need to add a field to the field scheme associated with the space where you want to configure this.

This is fairly new, as it was announced last year and rolled out at some point this year.

I got stuck with this a couple of times as I couldn't add a field to a screen/layout after I created it. Then I struggled for a while just to realize I first need to add it to a field scheme to be able to add it to a layout for specific work type(s) 😅

Anyway, are you seeing any specific issues? And also, can you maybe share which docs seem inconsistent so we can forward it to the support documentation team(s)? 👀

Cheers,

Tobi

Josh · Answer

On Company-managed Cloud the association is not on the field itself — it is through screens + field configurations:

1. Field configuration scheme (project) → field configuration → set the field Required/Optional/Hidden for that context.
 2. Screen scheme / issue type screen scheme → put the custom field on the Create/Edit/View screens for the work types that should show it.
 3. If you use contexts on the custom field, make sure the context includes this project (or “global”).

Quick check: open a Story → Admin gear → “Where is my field?” (or search the field on Create). If it says hidden by field configuration or missing from screen, that is the fix path.

Docs wander between “issue type” and “work type” language right now — same object. If you paste whether the field is missing on Create vs View, we can narrow to screen vs field config in one step.