Skip to main content
The Deno 2 Release Candidate is here
Learn more
Module

x/jira/src/agile/models/submittedVulnerabilitiesResult.ts>SubmittedVulnerabilitiesResult

A JavaScript/TypeScript wrapper for the JIRA Cloud, Service Desk and Agile REST API
MrRefactoring/jira.js
Latest
interface SubmittedVulnerabilitiesResult
import { type SubmittedVulnerabilitiesResult } from "https://deno.land/x/jira@v3.0.2/src/agile/models/submittedVulnerabilitiesResult.ts";

The result of a successful submitVulnerabilities request.

Properties

optional
acceptedVulnerabilities: string[]

The IDs of Vulnerabilities that have been accepted for submission.

A Vulnerability may be rejected if it was only associated with unknown project keys.

Note that a Vulnerability that isn't updated due to it's updateSequenceNumber being out of order is not considered a failed submission.

optional
failedVulnerabilities: { }

Details of Vulnerabilities that have not been accepted for submission, usually due to a problem with the request data.

The object (if present) will be keyed by Vulnerability ID and include any errors associated with that Vulnerability that have prevented it being submitted.

optional
unknownAssociations: { }[]

Associations (e.g. Issue Keys or Service IDs) that are not known on this Jira instance (if any).

These may be invalid keys (e.g. UTF-8 is sometimes incorrectly identified as a Jira issue key), or they may be for projects that no longer exist.

If a Vulnerability has been associated with any other association other than those in this array it will still be stored against those valid associations. If a Vulnerability was only associated with the associations in this array, it is deemed to be invalid and it won't be persisted.