Issue Summary

The partner is encountering an intermittent issue where the issueType field is missing from the response of the Jira Cloud API endpoint: The Jira Cloud platform REST API
 /rest/api/3/issue/<issue-id>?properties=*all&expand=names,schema
This issue is impacting the functionality of their app, Deep Clone, which relies on the issueType field to clone issues accurately. The problem is not limited to a single customer site but spans multiple instances, only affecting Team-Managed projects. The responses occasionally also show other fields (like assignee, priority, and properties) missing. Although the issue is sporadic and difficult to reproduce manually, the partner has gathered multiple affected timestamps, trace IDs, and instance URLs from their logs. They suspect the issue might be related to recent architectural changes involving Team-Managed projects, issue types, or work item transitions.

Steps to Reproduce

1. Make a GET request to the endpoint:
   /rest/api/3/issue/<issue-id>?properties=*all&expand=names,schema

1. Review the API response JSON payload.

1. Check whether the issueType field is missing, and log any anomalies.

1. If applicable, verify whether other fields such as assignee, priority, or properties are also absent

Expected Results

issueType field is present in the response.

Actual Results

Missing fields 

Workaround

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