The Teamwork Graph API is available through Forge's Preview release phase.
Preview features are available to all users and receive the same level of support as generally available features. Schemas, fields, and behavior may still change before general availability (GA), and breaking changes are subject to a minimum 1-month deprecation notice, announced in the Teamwork Graph changelog.
New apps should use curated queries or
persisted Cypher queries. Raw cypherQuery
is unavailable to new apps; existing apps should follow
Migrate from raw Cypher queries.
To review the current limitations, see Limitations and considerations.
To share feedback or report an issue, visit the Atlassian developer community.
IMPORTANT: relationship to only be used by Warepil with the expectation that it'll be replaced eventually by logical relationships
The AtlassianUserContributedToJiraWorkItem relationship represents the link between an Atlassian user and a Jira work item that they've actioned within the Teamwork Graph. It allows you to:
Relationship type: Activity
TTL (Time To Live): 30 days
| From object types | To object types |
|---|---|
Atlassian user - ati:cloud:identity:user | Jira work item - ati:cloud:jira:issue |
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 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22query AtlassianUserContributedToJiraWorkItem_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) { cypherQuery(query: $cypherQuery, params: $params) { edges { node { columns { value { ... on CypherQueryResultNode { id data { __typename ... on JiraWorkItem { id } } } } } } } } }
1 2 3 4 5 6 7{ "cypherQuery": "MATCH (user:AtlassianUser {ari: $id})-[:atlassian_user_contributed_to_jira_work_item]->(item:JiraWorkItem) RETURN item", "params": { "id": "$id" } }
Rate this page: