Project has issue

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 ProjectHasIssue relationship represents the link between a Jira project and its associated Jira issues within the Teamwork Graph. It allows you to:

Retrieve issues for a specific project
Find the parent project for a given Jira issue
Traverse and analyze project-issue relationships

Types

From Object Types	To Object Types
`Jira Project - ati:cloud:jira:project`	`Jira Issue - ati:cloud:jira:issue`

Cypher

Forward Query

GraphQL

1
2
query ProjectHasIssue_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on JiraIssue {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

Note

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 (project:JiraProject {ari: $id})-[:project_has_issue]->(issue:JiraIssue) RETURN issue",
  "params": {
    "id": "$id"
  }
}

Inverse Query

GraphQL

1
2
query ProjectHasIssue_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on JiraProject {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

Note

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 (project:JiraProject)-[:project_has_issue]->(issue:JiraIssue {ari: $id}) RETURN project",
  "params": {
    "id": "$id"
  }
}

Metadata

To Metadata

Name	Type	Properties
`assigneeAri`	Ari (`Message`)
`statusAri`	Ari (`Message`)
`issueAri`	Ari (`Message`)
`creatorAri`	Ari (`Message`)
`reporterAri`	Ari (`Message`)
`issueTypeAri`	Ari (`Message`)
`fixVersionIds`	`Long`	`repeated`

Relationship Metadata

Name	Type	Properties
`issueLastUpdatedOn`	`Long`
`sprintAris`	Ari (`Message`)	`repeated`

Nested Types

Ari

When filtering by ARI in GraphQL, it will behave as a String rather than a message as shown below.

Name	Type	Properties
`value`	`String`