18 Mar
2019
18 Mar
'19
9:20 a.m.
Module: check_mk
Branch: master
Commit: 69d580c062666a9cb88d6d0ce8d8495dae768d97
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=69d580c062666a…
Author: Ronny Bruska <rb(a)mathias-kettner.de>
Date: Fri Mar 15 15:24:10 2019 +0100
Fixed level and werk description
Change-Id: Id8f0093e91302e418001783263431d37f8143ac6
---
.werks/7195 | 31 ++++++++++++++++---------------
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/.werks/7195 b/.werks/7195
index 1f931d1..b6dabce 100644
--- a/.werks/7195
+++ b/.werks/7195
@@ -1,5 +1,5 @@
Title: Jira: Notification plugin
-Level: 1
+Level: 2
Component: notifications
Compatible: compat
Edition: cre
@@ -13,21 +13,22 @@ You can create issues for Host an Service Problems and optional set a
resolution
In Jira you have to add two custom fields to your project screen as described <a href
"https://confluence.atlassian.com/adminjiraserver/adding-a-custom-field-938847222.html">here</a>.
In Check_MK, under "WATO - Notifications", create a new notification rule and
select Jira.
+
Parameters to set:
-<i>JIRA URL<i>: The URL to your Jira environment
-<i>User Name<i>: Jira username
-<i>Password<i>: Jira password
-<i>Project ID<i>: The Project ID the issues should be created in
-<i>Issue type ID<i>: The issue type ID
-<i>Host custom field ID<i>: The first custom field ID you created in Jira
-<i>Service custom field ID<i>: The second custom field ID you created in
Jira
-<i>Monitoring URL<i>: URL of your Check_MK environment to create hyperlinks
back to Check_MK (eg. https://server/site)
-<i>Priority ID<i>: The priority ID (optional)
-<i>Summary for host notifications<i>: The summary the created host issue
should use (optional)
-<i>Summary for service notifications<i>: The summary the created service
issue shoud use (optional)
-<i>Label<i>: Label for Jira issues. If not set, 'monitoring' will be
used. (optional)
-<i>Activate resultion with following resolution transistion ID<i>: If set,
the created issue will be resolved with the configured resolution ID (optional)
-<i>Set optional timeout for connections to JIRA<i>: Timeout in seconds,
default is 10 (optional)
+LI:JIRA URL: The URL to your Jira environment
+LI:User Name: Jira username
+LI:Password: Jira password
+LI:Project ID: The Project ID the issues should be created in
+LI:Issue type ID: The issue type ID
+LI:Host custom field ID: The first custom field ID you created in Jira
+LI:Service custom field ID: The second custom field ID you created in Jira
+LI:Monitoring URL: URL of your Check_MK environment to create hyperlinks back to Check_MK
(eg. https://server/site)
+LI:Priority ID: The priority ID (optional)
+LI:Summary for host notifications: The summary the created host issue should use
(optional)
+LI:Summary for service notifications: The summary the created service issue shoud use
(optional)
+LI:Label: Label for Jira issues. If not set, 'monitoring' will be used.
(optional)
+LI:Activate resultion with following resolution transistion ID: If set, the created issue
will be resolved with the configured resolution ID (optional)
+LI:Set optional timeout for connections to JIRA: Timeout in seconds, default is 10
(optional)
You need different Jira IDs to open/resolve issues. There are different ways to get this
IDs:
LI: <a
href="https://confluence.atlassian.com/jirakb/how-to-get-project-id-fr…