Issue Summary

When creating an issue via a POST request, if the 'component' field value does not adhere to case sensitivity requirements (i.e., the case does not exactly match an existing component), the request fails. However, the error message returned is misleading, stating:

"No operation with name 'set' found. Valid operations are: ADD,SET,REMOVE,EDIT,COPY". 

This message does not address the actual issue, which is the non-existence of the specified component due to a case mismatch. The error messaging should be updated to accurately reflect that the component name must match case sensitively and that it is considered non-existent if not matched exactly.

Steps to Reproduce

1. Submit a POST request to the issue creation endpoint with a payload that includes the 'component' field, using a component name that mismatches the case of an actual, existing component name.

1. Note the returned error message, which inaccurately suggests an issue with operation names rather than the actual issue of a case-sensitive component name mismatch.

Expected Results

The error message returned by the API should clearly indicate that the issue is with the "component" field being incorrect. It should specify that the value provided for the component does not exist or is not valid in the context of the specified project.

Actual Results

Error message being thrown is

No operation with name 'set' found. Valid operations are: ADD,SET,REMOVE,EDIT,COPY

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available