Get All Issue Types For User Not Returning Project Key in Scope

[AlexHofer]

According to the docs here the Scope should contain a Project and in that an Id, a Key, and Name:

"scope": {
    "type": "PROJECT",
    "project": {
        "id": "10000",
        "key": "KEY",
        "name": "Next Gen Project"
    }
}

But our response only contains an Id:

"scope": {
    "type": "PROJECT",
    "project": {
        "id": "10030"
    }
}

We have tried adding this to the request url:
&expand=scope.project.key

Even though the endpoint doesn’t say what can be expanded but we were hoping it was just missing there.

Is there a different way we are supposed to be able to get that key from the response?

Edit: It appears this question has been asked before and the documentation is and has been incorrect for well over 2 and a half years so…super cool.

How to expand ProjectForScope while fetching issue types

I am using Get all issue types for user REST API to fetch issue types present in the system. I need to know which project these issue types belong to. I only get ‘scope.project.id’ in my response, but not ‘scope.project.key’ & ‘scope.project.name’ ( as seen in sample response). Do I need to send any expand parameters to get the key and name of the project? Thanks in advance.

[emre.toptanci]

I am struggling with the very same thing.

I am using the /rest/api/3/status endpoint and trying to get all statuses with their scopes and associated projects (with project ID and project Key). I couldn’t find a way yet. This endpoint returns the statuses but only with project IDs. No keys.