Missing validation when setting field values via JIRA API/CLI

[Joe Mallon]

Is it possible to set the list of values for a project-specific field via an API? If so, how?

[Holger Schimanski]

Do you want to manage the select option values like you do on the Project Specific tab? Or do you want to set the selected value of an isseu?

[Joe Mallon]

Is there a way to restrict the field values when the field is set via API/CLI? In that case, you can set the field to a non-standard value.

[Joe Mallon]

What I mean is that when I use the existing API to set the value of the field in an issue, its possible values are not restricted. When I set Priority via the API, I can only supply P1, P2, P3, or P4 as values. When I set a project-specific field in an issue, I can set it to any value, even one that is not specified in the project's list.

[Holger Schimanski]

Okay, got it – and you are right. There is a bug in current release. If you edit a value for a Project Specific Select Field via JIRA REST API, it is not validated to be one of the possible option values. This is only done, if you edit via JIRAs regular web interface.

I will fix this in the upcoming release 2.0.0, which will be released shortly.

[Holger Schimanski]

Version 2.0.0 released.