Inconsistency in create issue API

[Jakub Zimny]

I have a question regarding POST /rest/api/3/issue endpoint to create issues.
In the past, when non-existing component, fix or affects version was provided in fields, endpoint returned an error, for example: 
"Component name 'New_Component' is not valid";
At the moment, this validation seems to be removed for components field. Value for components field is added to Jira, and then the issue is created and API returns a success response. However, this validation still exists for fix/affects version field (which is also creatable on Jira screen, just like components) and creating an issue with new value still returns an error. I find it inconsistent and wanted to ask if you are also planning to remove validation for fix/affects version field?

Best regards,
Jakub Zimny

[Fabio Racobaldo _Herzum_]

Hi @Jakub Zimny ,

this seems to be a bug. Even a project admin need to create a component first and then use it through the UI. Please raise a support request to the Atlassian team https://support.atlassian.com/contact/#/

Fabio