forked from MrRefactoring/jira.js
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsubmitComponents.ts
29 lines (29 loc) · 1.27 KB
/
submitComponents.ts
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
/** The result of a successful submitDevopsComponents request.* */
export interface SubmitComponents {
/**
* The IDs of Components that have been accepted for submission.
*
* A Component may be rejected if it was only associated with unknown project keys.
*
* Note that a Component that isn't updated due to it's updateSequenceNumber being out of order is not considered a
* failed submission.
*/
acceptedComponents?: string[];
/**
* Details of Components that have not been accepted for submission, usually due to a problem with the request data.
*
* The object (if present) will be keyed by Component ID and include any errors associated with that Component that
* have prevented it being submitted.
*/
failedComponents?: {};
/**
* Project keys that are not known on this Jira instance (if any).
*
* These may be invalid keys (e.g. `UTF` is sometimes incorrectly identified as a Jira project key), or they may be
* for projects that no longer exist.
*
* If a Component has been associated with project keys other than those in this array it will still be stored against
* those valid keys. If a Component was only associated with project keys deemed to be invalid it won't be persisted.
*/
unknownProjectKeys?: string[];
}