forked from frakc/jira-move-task
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathstep.yml
130 lines (119 loc) · 3.19 KB
/
step.yml
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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
title: |-
jira-move-task-step
summary: |
This step update optional parameter and assign new status.
description: |
This step update optional parameter and move all tasks from one column to another . Mainly to quckly dump everything from code review to QA. It does NOT audit git log and thus move ALL task from column
website: https://github.com/frakc/jira-move-task
source_code_url: https://github.com/frakc/jira-move-task
support_url: https://github.com/frakc/jira-move-task/issues
host_os_tags:
- osx-10.10
- ubuntu-16.04
project_type_tags:
- ios
- android
type_tags:
- notification
is_requires_admin_user: false
is_always_run: false
is_skippable: true
run_if: ""
deps:
brew:
- name: git
- name: wget
- name: jq
apt_get:
- name: git
- name: wget
- name: jq
toolkit:
bash:
entry_file: step.sh
inputs:
- jira_user:
opts:
title: "JIRA User"
is_sensitive: false
summary: admin
description: |
User with privelige to move tasks
is_expand: true
is_required: true
- jira_token:
opts:
title: "JIRA API Token"
summary: Token created for supplied user
description: |
API token is used to authenticate with JIRA API.
It can be created here: https://id.atlassian.com/manage/api-tokens?_ga=2.43946604.875494627.1562923837-75487430.1434788493
is_expand: true
is_sensitive: false
is_required: true
- jira_url:
opts:
title: "JIRA Host"
summary: The host used to connect with JIRA API
description: |
ex.: https://[team].atlassian.net
is_expand: true
is_required: true
- to_status:
opts:
title: "JIRA resulting status"
summary: Task will be assigned to that status. Should be correct and should exist. Case sencitive
description: |
ex.: Ready for QA
is_expand: true
is_required: true
- from_status:
opts:
title: "JIRA starting status"
summary: Correct status if task. Only task with that status will be updated.
description: |
ex.: "Team Review"
is_expand: true
is_required: true
- jira_project_name:
opts:
title: "Jira project tag"
summary: Short project tag
description: |
ex. : BTTT
is_expand: true
is_required: true
- custom_jira_field:
opts:
title: " version field which will be updated"
summary: "set custom_jira_value to that field"
description: |
ex.: Build number
is_expand: true
is_required: false
- custom_jira_value:
opts:
title: " extra value"
summary: "that value will be inserted into custom_jira_field"
description: |
ex.: 15
is_expand: true
is_required: false
- changelogpath:
opts:
title: " path to write changelogs "
summary: "Task titles will be writen to specified file"
description: |
ex.: changelog.txt
is_expand: true
is_required: false
is_sensitive: false
- slack_webhoock:
opts:
title: " slack webhoock"
summary: "sends message listing transitioning tasks"
description: |
ex.: 15
is_expand: true
is_required: true
is_sensitive: false