Developer
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Last updated Oct 29, 2025

Project associated vulnerability

The ProjectAssociatedVulnerability relationship represents the link between a Jira project and an external vulnerability within the Teamwork Graph. It allows you to:

  • Retrieve external vulnerabilities associated with a specific Jira project
  • Find which Jira projects are associated with an external vulnerability
  • Traverse and analyze project-vulnerability relationships

Relationship type: Canonical

From object typeTo object type
Jira project - ati:cloud:jira:projectExternal vulnerability - ati:cloud:jira:vulnerability

Cypher

We recommend using parameterized Cypher queries rather than placing parameters directly in the query string. This helps improve performance.

Forward query

GraphQL
1
2
query ProjectAssociatedVulnerability_CypherQuery($cypherQuery: String!, $params: JSON!) {
 graphStore @optIn(to: ["GraphStore", "GraphStoreCypherQueryV2"]) {
  cypherQueryV2(query: $cypherQuery, params: $params) {
   edges {
    node {
     columns {
      key
      value {. on GraphStoreCypherQueryV2NodeList {
        nodes {
         data {. on DevOpsSecurityVulnerabilityDetails {
           id
          }. on ExternalVulnerability {
           id
          }
         }
        }
       }. on GraphStoreCypherQueryV2AriNode {
        data {. on DevOpsSecurityVulnerabilityDetails {
          id
         }. on ExternalVulnerability {
          id
         }
        }
       }. on GraphStoreCypherQueryV2BooleanObject {
        bool_val: value
       }. on GraphStoreCypherQueryV2IntObject {
        int_val: value
       }. on GraphStoreCypherQueryV2FloatObject {
        float_val: value
       }. on GraphStoreCypherQueryV2StringObject {
        str_val: value
       }
      }
     }
    }
   }
  }
 }
}
Params
1
2
{
 "cypherQuery": "MATCH (project:JiraProject {ari: $id})-[:project_associated_vulnerability]->(vulnerability:GraphVulnerability) RETURN vulnerability",
 "params": {
  "id": "$id"
 }
}

Inverse query

GraphQL
1
2
query ProjectAssociatedVulnerability_CypherQuery($cypherQuery: String!, $params: JSON!) {
 graphStore @optIn(to: ["GraphStore", "GraphStoreCypherQueryV2"]) {
  cypherQueryV2(query: $cypherQuery, params: $params) {
   edges {
    node {
     columns {
      key
      value {. on GraphStoreCypherQueryV2NodeList {
        nodes {
         data {. on JiraProject {
           id
          }
         }
        }
       }. on GraphStoreCypherQueryV2AriNode {
        data {. on JiraProject {
          id
         }
        }
       }. on GraphStoreCypherQueryV2BooleanObject {
        bool_val: value
       }. on GraphStoreCypherQueryV2IntObject {
        int_val: value
       }. on GraphStoreCypherQueryV2FloatObject {
        float_val: value
       }. on GraphStoreCypherQueryV2StringObject {
        str_val: value
       }
      }
     }
    }
   }
  }
 }
}
Params
1
2
{
 "cypherQuery": "MATCH (project:JiraProject)-[:project_associated_vulnerability]->(vulnerability:GraphVulnerability {ari: $id}) RETURN project",
 "params": {
  "id": "$id"
 }
}

Materialization via Cypher Experimental

This materialization rule automatically creates project_associated_vulnerability relationships by traversing from Jira projects through their security containers to find associated vulnerabilities.

Cypher
1
2
// Materialization Rule: security-container-associates-project-to-vulnerability
MATCH (project:JiraProject {ari: $id})
MATCH (project)-[rel0:project_associated_to_security_container]->(container:GraphSecurityContainer)
MATCH (container)-[rel1:security_container_associated_to_vulnerability]->(vulnerability:GraphVulnerability)
RETURN vulnerability AS ret, MAX(rel1.lastUpdated) AS lastUpdated

Metadata

To metadata

Container

Ari

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

NameTypeDescription
valueStringThe ARI string value identifying the container or resource.

VulnerabilityStatus

NameInternal NameIndexDescription
not-setSTATUS_NOT_SET0No status has been set for this vulnerability.
unknownSTATUS_UNKNOWN170Vulnerability status cannot be determined.
closedSTATUS_CLOSED180Vulnerability has been resolved and closed.
ignoredSTATUS_IGNORED190Vulnerability has been acknowledged but intentionally ignored.
openSTATUS_OPEN200Vulnerability is active and requires attention.

VulnerabilitySeverity

NameInternal NameIndexDescription
not-setSEVERITY_NOT_SET0No severity level has been assigned to this vulnerability.
unknownSEVERITY_UNKNOWN150Vulnerability severity cannot be determined.
lowSEVERITY_LOW160Low severity vulnerability with minimal security impact.
mediumSEVERITY_MEDIUM170Medium severity vulnerability with moderate security impact.
highSEVERITY_HIGH190High severity vulnerability with significant security impact.
criticalSEVERITY_CRITICAL200Critical severity vulnerability requiring immediate attention.

VulnerabilityType

NameInternal NameIndexDescription
not-setTYPE_NOT_SET0No vulnerability type has been set.
dastTYPE_DAST100Dynamic Application Security Testing vulnerability.
sastTYPE_SAST110Static Application Security Testing vulnerability.
scaTYPE_SCA120Software Composition Analysis vulnerability found in dependencies.
unknownTYPE_UNKNOWN130Vulnerability type cannot be determined.

Rate this page: