This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
/
config.ini
157 lines (120 loc) · 6.64 KB
/
config.ini
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
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
# rt2jira configuration file
# NOTE: Please review and modify EACH of these settings in this INI file, before running the script.
# This section defines the settings required to pull tickets from RT
[rt]
# URL of REST API for RT
api_url_prefix = https://rt.server.com/REST/1.0/
# Username to login to RT
username = rt_username
# Password to login to RT
password = rt_password
# Search query to feed into the REST API to pull relevant tickets down to be ported as JIRA tickets
api_search_suffix = search/ticket?query=Queue+%3D+%27RT-Queue-Name%27+AND+LastUpdated+%3E+%27-5+days%27&orderby=LastUpdated&format=l
# The URL prefix to display RT tickets, given a Ticket ID
url_ticket_display_prefix = https://rt.server.com/rt/Ticket/Display.html?id=
# When correlating RT tickets with the same Subject line, make sure the new ticket IDs are within +/- the value listed below, when correlating.
# This helps address issues where two RT tickets that are months apart but have the same generic Subject line do not get mistakenly correlated
# together in the same JIRA ticket.
# Note: It is still possible for this mistake to occur, if two separate RT tickets are filed with generic Subjects and within a very short-timespan of
# one another. In that scenario, your options are to either: (a) ask the requesters to pick specific Subject lines or (b) reduce the value of the
# setting shown below.
ticket_id_correlation_range = 10
# The timestamp of the most recent RT ticket comment ported to JIRA
# NOTE: Please leave this value empty, during the first run of the script.
last_fetched_timestamp =
# This section defines the settings required to push tickets to JIRA
[jira]
# URL of JIRA Interface
api_url_prefix = https://jira.server.com:8443
# Username to login to JIRA
username = jira_username
# Password to login to JIRA
password = jira_password
# Specify whether the script should perform SSL server certificate verification, when connecting to JIRA
verify = False
# The JIRA project ported RT tickets should be created under
project = ENG
# The JIRA issue type to use, when creating new tickets
issue_type = Bug
# The JIRA component ported RT tickets should be created under
component = Other
# The set of JIRA projects to search against, when finding JIRA users to map to from RT users.
# Note: This can be a comma separated list of JIRA projects, like:
; find_user_projects = FOO,BAR,BAZ
find_user_projects = ENG
# The algorithm to use when finding matching users in JIRA, based on the RT ticket creator specified.
find_user_algo_type_description = 0
# The algorithm to use when finding matching users in JIRA, based on the RT ticket commentor specified.
find_user_algo_type_comment = 0
# When trying to find matching users in JIRA, based on an RT username, use this local mapping as an override,
# if defined. This helps in cases where JIRA and RT are not using the same usernames.
# For example:
; find_user_mapping = [("rt_username", "jira_username"), ("jsmith", "john.smith")]
# Note: If unsure, please leave this value empty.
find_user_mapping =
# When a JIRA ticket is created, add these additional custom fields to the ticket.
# For example:
; create_fields = [("customfield_10902", "None")]
# Note: If unsure, please leave this value empty.
create_fields =
# When an RT ticket is marked as resolved, use the following transition name to mark the JIRA ticket as resolved.
resolve_transition_name = Resolve
# When an RT ticket is marked as resolved, use the following resolution type to signify the JIRA ticket is resolved.
resolve_resolution_name = Fixed
# When a JIRA ticket is resolved, provide the following comment in the resolution.
resolve_comment = Resolving ticket.
# When a JIRA ticket is resolved, add these additional custom fields to the ticket.
# For example:
; resolve_fields = [("customfield_10902", "None")]
# Note: If unsure, please leave this value empty.
resolve_fields =
# When an RT ticket is reopened, use the following transition name to mark the JIRA ticket as reopened.
reopen_transition_name = Reopen Issue
# When a JIRA ticket is reopened, provide the following comment when reopening the ticket.
reopen_comment = Reopening ticket.
# When running the auto-resolve.py script, this is the number of days to leave a JIRA ticket
# in Open state before marking it as automatically resolved.
auto_resolve_after_days = 5
# Upon JIRA ticket creation, should the security level of the ticket be modified?
modify_security_level = False
# If modify_security_level is True, then what level should the created JIRA ticket be set to?
# To remove any security level, then set this value to:
; target_security_level = None
# Otherwise, specify a specific name for the security level.
target_security_level = None
# If modify_security_level is True and the RT ticket and/or comments contain the full-word string
# specified in the original_security_level, then any corresponding JIRA ticket will be set to
# the specified original_security_level, which is the default security level of the JIRA ticket
# upon creation.
# To completely disable this functionality, then set this value to:
; original_security_level = None
# Otherwise, specify a specific name for the security level.
original_security_level = None
# For every new JIRA ticket created, apply the following label to the ticket.
# To completely disable this functionality, then set this value to:
; new_issue_label = None
# Otherwise, specify a specific label to apply to the ticket.
new_issue_label = None
# Everytime a new comment is added to an existing JIRA ticket, apply the following label to the ticket.
# To completely disable this functionality, then set this value to:
; new_comment_label = None
# Otherwise, specify a specific label to apply to the ticket.
new_comment_label = None
# When running the auto-reply.py script, search for the max number of related JIRA tickets specified.
auto_reply_max_results = 5
# When referencing tickets in the auto-reply.py script, use the following JIRA URL prefix.
jira_url_prefix = https://jira.server.com:8443
# When running the auto-reply.py script, use the following ticket description as the reply template.
# Note: This must be set to a valid JIRA ticket; otherwise, the auto-reply.py script will fail.
auto_reply_template_ticket = None
# When creating any new JIRA tickets, the following set of users will always be added as watchers
# to the ticket.
# This list must be comma separated, for example:
; create_watchers = john.smith,jane.doe
# If disabled, set to None.
create_watchers = None
[sanity]
# TODO: Please change this setting from False to True, after all other settings have been reviewed/modified
reviewed = False
# Change this to 'True' if you want more verbose debugging visible in the console
debug = False