-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add link to service in created JIRA issue #42
Comments
Just an additional detail we just noticed: The screenshot from above is from an automatically created issue (Icinga2 Check > Alert > Notification which created JIRA issue - without any manual intervention). But for cases where we created an issue from within the Icingaweb2 GUI, the resulting ticket looks like it contains the link back to the service we're missing in the automatically created issue: |
I confirm here the same behavior. Since our clients see in benefit in jumping from links back to Icinga2, i would be interested in further development. System Description: Debuglog shows usual behavior, but there is this warning: debuglog`` [2020-01-21 11:33:51 +0100] notice/Process: PID 17907 ('/usr/bin/icingacli' 'jira' 'send' 'problem' '--ack-author' 'Automation' '--description' 'Server is Down' '--host' 'test dummy server' '--issuetype' 'Incident' '--project' 'IN' '--state' 'DOWN' '--summary' 'test dummy server ist im Status DOWN') terminated with exit code 255 |
@Obivatelj so your issue with the trace you posted should be fixed with Icinga Web 2.8 Icinga/icingaweb2#4065 :) Concerning the topic of the issue: my plan would be to use the description template, that is added for all manually sent notifications to Jira, and just add that as a template for all others too. So basically the link should be found in all descriptions, like in this very realistic example below:
|
@mrimann : I need your help to configuration icinga2 with JIRA module. as I want if any issue occour into host or service JIRA ticket should create automatically. Below is host configuration file. object Host "jira.com" { Done configuration into notification.conf as below. apply Notification "jira" to Host { apply Notification "jira" to Service {
|
Hey @kaurav1108 would you please take this kind of question to the community forum. If @mrimann wants to answer your question, they can do so on the forum. |
We configured the Icingaweb2 module for JIRA and it creates tasks for low-priority issues in JIRA. They end up in our Ops-Pool, basically a queue of tickets that $someone from our team will work.
These created issues look like the one in the screenshot below:
What we're missing is a link to the service's detail view in Icingaweb2, so the user working on those queued issues can just follow the link to see the current status of the service that triggered the notification / creation of the JIRA issue.
I've not found an easy solution for this in the docs - but maybe I'm missing something and it's just a question of adding some config?
The text was updated successfully, but these errors were encountered: