git.issues.getOne issue with its comments
Request syntax
GET /git/api/repositories/{repoId}/issues/{number}Path parameters
repoIdRequiredstring
Constraints: uuid
numberRequirednumber
Constraints: integer, min 1
Response
200 with the issue (as in `list`), `comments` being the comments themselves, each with id, authorIamUserId, body and createdAt.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
idAlwaysstring
The issue idorgIdAlwaysstring
The organization it belongs torepoIdAlwaysstring
The repository it belongs tonumberAlwaysnumber
Its number, shared with pull requests in one sequence per repositorytitleAlwaysstring
The titlebodyAlwaysstring, may be null
The description (Markdown); null when there is nonestateAlwaysone of open, closed
Whether it is open or closedstateReasonAlwaysone of completed, not_planned, may be null
Why it was closed (done, or not going to be done); null while openauthorIamUserIdAlwaysstring, may be null
The IAM user who opened it; null once that user is deletedclosedAtAlwaysstring, may be null
When it was closed (ISO 8601); null while opencreatedAtAlwaysstring
When it was opened (ISO 8601)updatedAtAlwaysstring
When it last changed or was commented on (ISO 8601)labelsAlwaysarray of object
The labels it carrieslabels[].idAlwaysstring
The label idlabels[].nameAlwaysstring
The label namelabels[].colorAlwaysstring
Six hex digits, without #assigneeIamUserIdsAlwaysarray of string
The IAM users it is assigned tocommentsAlwaysarray of object
Its comments, oldest firstcomments[].idAlwaysstring
The comment idcomments[].orgIdAlwaysstring
The organization it belongs tocomments[].issueIdAlwaysstring
The issue it is oncomments[].authorIamUserIdAlwaysstring, may be null
The IAM user who wrote it; null once that user is deletedcomments[].bodyAlwaysstring
The comment (Markdown)comments[].createdAtAlwaysstring
When it was written (ISO 8601)
Checked against the handlers: every route test validates their answers against this schema.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow git:ListIssues on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud git issues get repoId numbercurl -X GET "https://console.platform-development.deutschecloud.app/git/api/repositories/repoId/issues/number" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_git_issues_get.