Issue Summary

The GET /rest/api/3/issue/{issueIdOrKey} endpoint occasionally returns an HTTP 200 response with required fields (such as issuetype) missing from the payload, even when the request is sent with the failFast=true query parameter. Per the public REST API documentation, failFast=true should cause the entire request to fail if any field fails to load, so the observed behavior contradicts the documentation.

Steps to Reproduce

1. On a Cloud tenant experiencing high API request load, create a new work item via POST /rest/api/3/issue.
2. Immediately fetch the newly created work item using GET /rest/api/3/issue/{issueIdOrKey}?failFast=true.
3. Inspect the response payload.

Expected Results

Either:

• The response is HTTP 200 with a complete payload that includes all standard fields (e.g. issuetype, summary, status, project, created), OR
• The request fails with a non-2xx response, as documented for failFast=true.

Actual Results

The endpoint returns HTTP 200, but the payload is missing fields that should always be present on a created issue (e.g. issuetype is absent), instead of failing the request as the failFast=true contract states.

Workaround

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