-
Type:
Suggestion
-
Resolution: Timed out
-
Component/s: Compass - Components
-
1
Issue Summary
Get component endpoint: /rest/api/3/component/{id} works differently for classic Jira components and Compass components. For classic components, in the response we get project and{{ projectId}} . However, this information is excluded when we call the endpoint for the Compass component.
Documentation: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-components/#api-rest-api-3-component-id-get
It would be helpful if the response for the Compass component also included the project, as these two types of components currently have to be handled differently.
Steps to Reproduce
- Call the GET /rest/api/3/component/{id} endpoint for the Compass component
Expected Results
Getting response similar to classic component, including project and projectId.
Snippet from response for the classic component :
"assigneeType":"PROJECT_DEFAULT", "realAssigneeType":"PROJECT_DEFAULT", "isAssigneeTypeValid":false, "project":"JSM", "projectId":10001
Actual Results
Response:
{
"self": "xxxx/rest/api/3/component/10016",
"id": "10016",
"name": "test-compass-component",
"isAssigneeTypeValid": false,
"ari": "ari:cloud:compass:xxxx",
"metadata":
{
"typeId": "SERVICE",
"compassComponentState": "ACTIVE",
"compassComponentVersion": "3" }
}
Workaround
Currently there is no known workaround for this.