forked from MrRefactoring/jira.js
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcreateIssue.ts
64 lines (62 loc) · 1.78 KB
/
createIssue.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
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
import {
Document, IssueUpdateDetails, Project, TimeTrackingDetails,
} from '../models';
export interface CreateIssue extends Omit<IssueUpdateDetails, 'fields'> {
/**
* Whether the project in which the issue is created is added to the user's **Recently viewed** project list, as shown
* under **Projects** in Jira. When provided, the issue type and request type are added to the user's history for a
* project. These values are then used to provide defaults on the issue create screen.
*/
updateHistory?: boolean;
/**
* List of issue screen fields to update, specifying the sub-field to update and its value for each field. This field
* provides a straightforward option when setting a sub-field. When multiple sub-fields or other operations are
* required, use `update`. Fields included in here cannot be included in `update`.
*/
fields: {
[key: string]: any;
summary: string;
project: Partial<Project>;
issuetype: {
id?: string | number;
name?: string;
};
parent?: {
[key: string]: any;
key?: string;
};
components?: Array<{
[key: string]: any;
id?: string | number;
}>;
description?: string | Document;
reporter?: {
[key: string]: any;
id?: string | number;
};
fixVersions?: Array<{
[key: string]: any;
id?: string | number;
}>;
priority?: {
[key: string]: any;
id?: string | number;
};
labels?: string[];
timetracking?: TimeTrackingDetails;
security?: {
[key: string]: any;
id?: string | number;
};
environment?: any;
versions?: Array<{
[key: string]: any;
id?: string | number;
}>;
duedate?: string;
assignee?: {
[key: string]: any;
id?: string | number;
};
};
}