Allowed values for fields which are not on create/edit screen

[OpsHub Tech]

While using REST APIs for getting fields meta data, when the fields are present in create/edit screen, we can get allowed values for multiselect/single select type of fields, using create/edit meta APIs

But if the field is not present the /fields API does not give allowed values for the mutli/single select fields.

Is there any way we can get the allowed values for the fields which are not on create/edit screen.

[Marc - Devoteam]

Hi @OpsHub Tech 

Welcome to the community.

If this is based on an issue, then this is not possible as then you only have the fields available based on the issue.

You could create custom fields with a default value to store meta data. If tis is multiple data points create a field for each data point.

The context of the fields should be global, then for every created issue the value will be set, even if they are not on any screen.

[Hans Polder _Devoteam_]

@OpsHub Tech ,

I am not a API-expert, but the workaround that comes to my mind would be:

1) Create a separate screen that contains all the fields you want to stay hidden in the normal screens. Associate it with another project that is not open to the public but shares the rest of the configuration of your intended project

2) In the API-calls to retrieve the field values, you could use this 'dummy screen' to retrieve all the values, and then set them in the intended screen/ticket.

I don't know if it would work, but that's what I would try!

After figuring it out, you could try to find better/cleaner solutions than above, at least I'd try figuring out if I could get the allowed values this way and move from there.