Get an ALM issue

Requires Requirement:Read and an active integration in the current project. Use the ALM issue key or the provider's own issue ID, not a requirement's externalIssueId. For linked requirements use sourceId; for defects use issueId. Use a Jira issue key or an Azure DevOps numeric work-item ID.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
int64
required

Existing project integration ID from the UI or the integration record's id in GET /v2/alm/connections/integrations (configuration endpoint outside this reference). Not a connection ID or external project ID.

string
required

ALM issue key or the provider's own issue ID. For linked requirements use sourceId, not externalIssueId; for defects use issueId. A requirement's numeric externalIssueId is not a substitute for its Jira key here. Azure DevOps uses a numeric work-item ID as a string. Xray is not supported.

Headers
uuid

Account UUID, when needed to resolve account context.

int64

Organization ID, when needed to resolve organization context.

int64
required

Project containing the preconfigured ALM integration.

Responses

default

Request failed. Check authentication, project access, operation permission, integration ownership, and provider access. Provider failures are not guaranteed to use a uniform status or response body.

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Choose an example:
application/json