Hi @clouless
Sorry for the delayed response.
In your proposed solutions example, which returns the same field associated to the project with different work types => Are there still underlying context with a contextId?
With new model, there is no guarantee that there is context for the field returned from this API as the goal of new Field Scheme model is to have fields will be directly associated with Field scheme. This means users can no longer restrict a field to a project by deleting its global context and replacing it with a project-limited one. This can result in having fields returned from this proposed API and does not have applicable context for the given project and work types. (As started in RFC-103: Jira Field Configuration Overhaul: Admin Experience and API Changes)
Once everyone is onboarded to use new Field Schemes, we are going to make sure there is always global context exist for all the fields, but this won’t happen until the old Field Config Schemes are fully deprecated.
Thanks!
Leanne