The Teamwork Graph API is coming soon. The relationship types documented here are indicative of what will be available in the Graph via the Teamwork Graph API. Please note that relationships, their properties, and functionality may change before and during the Early Access Program.
Interested in early access? Express your interest in joining the EAP
The IssueAssociatedDeployment relationship represents the link between a Jira issue and an external deployment within the Teamwork Graph. It allows you to:
| Category | Canonical |
The TTL (Time To Live) specifies the retention period for relationship data, determining how far back in time the relationship remains queryable.
| From Object Types | To Object Types |
|---|---|
Jira Issue - ati:cloud:jira:issue | External Deployment - ati:cloud:jira:deployment |
External Deployment - ati:cloud:graph:deployment |
1 2query IssueAssociatedDeployment_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) { cypherQuery(query: $cypherQuery, params: $params) { edges { node { columns { value { ... on CypherQueryResultNode { id data { __typename ... on DeploymentSummary { id } ... on ExternalDeployment { id } } } } } } } } }
We recommend sending parameterized Cypher queries as below instead of embedding the parameters directly in the query string. This approach will help ensure better performance.
1 2{ "cypherQuery": "MATCH (issue:JiraIssue {ari: $id})-[:issue_associated_deployment]->(deployment:GraphDeployment) RETURN deployment", "params": { "id": "$id" } }
1 2query IssueAssociatedDeployment_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) { cypherQuery(query: $cypherQuery, params: $params) { edges { node { columns { value { ... on CypherQueryResultNode { id data { __typename ... on JiraIssue { id } } } } } } } } }
We recommend sending parameterized Cypher queries as below instead of embedding the parameters directly in the query string. This approach will help ensure better performance.
1 2{ "cypherQuery": "MATCH (issue:JiraIssue)-[:issue_associated_deployment]->(deployment:GraphDeployment {ari: $id}) RETURN issue", "params": { "id": "$id" } }
| Name | Type | Properties |
|---|---|---|
state | DeploymentState (Enum) | |
environmentType | EnvironmentType (Enum) | |
author | Author (Message) |
When filtering by ARI in GraphQL, it will behave as a String rather than a message as shown below.
| Name | Type | Properties |
|---|---|---|
value | String |
| Name | Internal Name | Index |
|---|---|---|
not-set | DEPLOYMENT_STATE_NOT_SET | 0 |
pending | DEPLOYMENT_STATE_PENDING | 10 |
in_progress | DEPLOYMENT_STATE_IN_PROGRESS | 20 |
successful | DEPLOYMENT_STATE_SUCCESSFUL | 30 |
failed | DEPLOYMENT_STATE_FAILED | 40 |
cancelled | DEPLOYMENT_STATE_CANCELLED | 50 |
rolled_back | DEPLOYMENT_STATE_ROLLED_BACK | 60 |
unknown | DEPLOYMENT_STATE_UNKNOWN | 70 |
| Name | Internal Name | Index |
|---|---|---|
not-set | ENVIRONMENT_TYPE_NOT_SET | 0 |
unmapped | ENVIRONMENT_TYPE_UNMAPPED | 10 |
development | ENVIRONMENT_TYPE_DEVELOPMENT | 20 |
testing | ENVIRONMENT_TYPE_TESTING | 30 |
staging | ENVIRONMENT_TYPE_STAGING | 40 |
production | ENVIRONMENT_TYPE_PRODUCTION | 50 |
Rate this page: