Icon

Comments have been closed on this page. Please use AppMon & UEM Plugins forum for questions about this plugin.

Overview

The JIRA Action plugin integrates dynaTrace in your exisiting JIRA ticketing system. The plugin creates a new JIRA Issue for Alerts triggered by dynaTrace and includes detailed information about the Incident in the created JIRA Ticket.


This plugin is a showcase plugin to better understand how to build custom action plugins for dynaTrace.
A detailed Step-By-Step Guide explains how to build a plugin like this. The implementation of this plugin can easily be changed to create tickets in other ticketing systems such as Bugzilla, Trac, etc.

Icon

A new version of the plugin has been uploaded which now supports JIRA JIRA 5.2+

Plugin Details

Plug-In Versions


JIRA Action Plugin (compatible with dynaTrace >= 5.5)
JIRA Action Plugin for JIRA 5.2 (compatible with dynaTrace >= 5.5)
JIRA Action Plugin for JIRA 6 v. 0.0.9 (compatible with dynaTrace >= 5.5)

JIRA REST Action Plugin 0.1.0 (updated on January 30th, 2015, removing dependency on CURL and temporary file), tested against JIRA 6.1.4...

JIRA REST Action Plugin 0.1.1 (including custom fields)

Note : make sure the "issue type" you use either has no custom mandatory field or the custom mandatory fields have default values The plugin will try to create an "issue" with only the following data : "Summary", "Description" (plus "Reporter" and "Assignee" if you provide values for them).

Author(s)

Roman Spitzbart (roman.spitzbart@dynatrace.com)
Rajesh Jain (rajesh.jain@dynatrace.com)
Jan-Hendrik Wolf

Laurent IZAC (laurent.izac@dynatrace.com)

License

dynaTrace BSD

Support

Not Supported

Known Problems

 

Release History

2010-04-27 Initial Release

JIRA 5.2 Integration Explained

Installation

Extract the downloaded zip file to a local folder. Then import the Plugin into the dynaTrace Server. For details how to do this please refer to the dynaTrace documentation.

Contribution

Feel free to contribute any changes on Github

  1. Anonymous (login to see details)

    Moved the comment to forums

  2. Anonymous (login to see details)

    Any Chance this is going to be updated soon to support the REST API?

  3. Anonymous (login to see details)

    Has anyone tested it with JIRA v6.1+?

  4. Anonymous (login to see details)

    Hi,

    I modified the plugin. Now it works with JIRA 6+ and uses the REST-API with a curl-command. Not the best way, but the easiest.

    Shall I upload it anywhere? Is someone interested?

    Regards,

    Jan

    1. Anonymous (login to see details)

      Jan-hendrik Wolf,

      Have you uploaded this anywhere I can get a hold of it?  I was trying to develop something myself that does the same thing.  I agree it's not the best way, but it seems to be the route my JIRA Administrators prefer.

       

      David

      1. Anonymous (login to see details)

  5. Anonymous (login to see details)

    Hi Jan - Great News. I just sent you an email. Please send me the updated plugin and I can upload it for you

  6. Anonymous (login to see details)

    Hi Jan,

     

    Please help me to get incident details from Incident.

    I want method name used  to retrieve Incident details from Incident.

     

     Regards,

    Jalpesh

  7. Anonymous (login to see details)

    I have created incident  on BTM threshold.

    I want BTM vaules in plugin.

    So please tell me which method is used  to retrieve incident  values in plugin.

    So that I will modify plugin as per requirement.

     

    Regards,

    Jalpesh

     

     

  8. Anonymous (login to see details)

    Hi Jalpesh,

    the easiest way to get this method is by downloading the plugin in check it out on your dynaTrace Server. You will get the sourcecode than.

    Another way is to read the java doc, which can be found here: Developing a User Plugin

    I would recommend to do this two things first.

     

    Regards,

    Jan

     

  9. Anonymous (login to see details)

    Hi all,

    I uploaded a new release of the REST plugin (v. 0.1.0, also on GitHub), removing dependency on CURL and temporary file.

    It also uses project Key and Issue Type (rather than Ids).

    It is using the following implementation of a full Java client : https://github.com/rcarz/jira-client

    It has been tested against JIRA 6.1.4 over an https connection.

    Regards

    --

    Laurent IZAC

  10. Anonymous (login to see details)

    Dear Sir,

     

    It great plugin and working fine with HTTP Because we are request to make use HTTPS instead, after we created selfsign cert on dynatrace server, register it on JIRA server and seems pass openssl testing, but encounter below error when we try to raise a ticket to JIRA via HTTPS. Would you please advise if any details steps we can follow up for HTTPS case?

     

    Status: 501 (peer not authenticated peer not authenticated)

    Message: Plugin was unable to execute target service

     

    Tks for your help first

     

    Tan Bing

  11. Anonymous (login to see details)

    I created a fork of this plugin for a customer that required "Due Date".  Along the way I made other changes such as translating German to English, simplifying and improving (in my opinion, at least) the formatting of messages, and allowing for separate specification of the Reporter and Assignee values.

    If there is interest in merging my changes into the main branch, or if anyone wants to try it out in the meantime, it can be found on my GitHub account:

    https://github.com/dmauney/Dynatrace/tree/master/plugins/com.dynatrace.diagnostics.jira.CreateIssueActionPlugin_0.0.10

    Thanks,

    dave

     

     

     

    1. Anonymous (login to see details)

      Hi,

      as I understand, you forked release 0.0.1; which is the oldest one.

      Make sure to check later updates (0.0.4, 0.0.9 and 0.1.0)...

       

      regards

      --

      Laurent

      1. Anonymous (login to see details)

        Hi Laurent,

        I forked 0.0.9 (which was the latest when I started this project) to create 0.0.10.

        Thanks,

        dave

  12. Anonymous (login to see details)

    Hi there,

     

    Great thread and very insightful.  I would like to know though if anyone has ever made this work with dynaTrace v6.2 and JIRA v6.3.9.

    Please note that I've been getting errors even with the latest update of the plugin.

     

    Thanks,

     

    1. Anonymous (login to see details)

      Hi Sean,

      which errors do you get?

      I am using a slightly modified plugin on version 6.3.15 and 6.4.12 and it works fine.

      Regards,

      Jan

  13. Anonymous (login to see details)

    Hi Jan,

     

    Thanks for your response... I get the error below, and this is while I'm testing the plugin.

    Status: 501 (400 Bad Request: {"errorMessages":[],"errors":{"components":"Component/s is required.","reporter"...)
    Message: Plugin was unable to execute target service

    I did check my inputs, however I'm wopndering if I have to add the "components" on the plugin properties.


    Regards,

    Sean

    1. Anonymous (login to see details)

      Hi Sean,

      yes, your JIRA expects the field components filled.

      This field is not implemented in the JIRA plugin...

      I have an own version, where you can set component & environment.

      I also implemented two other things:

      • updating existing tickets with same name and a comment
      • make a transition in JIRA (like in Progress or resolved or whatever)

      But I have to warn you. My developing skills aren't really the best, the comments are in german and I didn't use the actual fork of Dave (wink)

       

      Unfortunately I have no possibility to upload it here...

      Regards,

      Jan

  14. Anonymous (login to see details)

    Jan,

     

    It's not a problem at least I'll be having something to work with. I don't know but you can drag and drop the file on to this text field. Alternativley here's my work email, seans6@discovery.co.za, and if you don't mind you can contact me and we'll take it from there.

     

    Regards,

    Sean

  15. Anonymous (login to see details)

    Hi Sean

    I added a new field where you can specify key=value pairs separated by & (like for URL parameters) in the following format :

    customfield_1=blah blah&customfield_2=ABCD&customfield_3=something else

     

    Note : you have to make sure you specify the exact custom field keys and expected values (in case they are taken from a fixed list).

     

    I attached the updated version (0.1.1). You should unzip it first.

    Could you give it a try and tell me how it works for you ?

     

    Regards

    --

    Laurent

    1. Anonymous (login to see details)

      Good day Laurent,

       

      Thank you for your assistance, I'll definitely give it a try and let you know.

       

      Regards,

      Sean

       

    2. Anonymous (login to see details)

      Hi Laurent,

      With regards to custom fields, it seems that if the JIRA field is a select box (dropdown), the plugin can't set the value. Have you looked into this or have an idea on how to edit the code to make it work?

      Regards,
      Gabriel 

      1. Anonymous (login to see details)

        It should work when using ids and not labels appearing in the dropdown...

        1. Anonymous (login to see details)

          Hey Laurent, thanks for the reply. I have just tried it with id, but no luck. Please check the log below, no ticket has been created on JIRA.

          2016-01-29 21:14:05 INFO [CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action] ----------------------Executing JIRA - Create Issue Action Plugin-----------------------------
          2016-01-29 21:14:05 INFO [CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action] Parameters are: jiraURL= <JIRAURL>, jiraUsername= <JIRAUSER>, jiraPassword= *******, jiraProjectName= TES, jiraIssueTypeName= Bug
          2016-01-29 21:14:05 INFO [CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action] number_of_incidents= 1
          2016-01-29 21:14:06 INFO [CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action] summary=teste jira2
          2016-01-29 21:14:06 INFO [CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action] description=
          -
          ||Details|| ||
          |Severity| Informational|
          |Start Time| 2016-01-29 21:13:30|
          |End Time| -|
          |Duration| -|
          |Status| Open|
          |Server| <SERVERIP> |
          ||Incident Rule|| ||
          |Name | teste jira2|
          |Trigger Condition | ThreadPoolRuntime-ExecuteThreadTotalCount - teste jira|
          ||Violations|| ||
          | Measure|ThreadPoolRuntime-ExecuteThreadTotalCount - teste jira <all-applications> (<SERVERNAME>)|
          | Affected Server| <SERVERNAME>|
          | Critical Threshold| 200.00num|
          | Warning Threshold| -| \n| <SERVERNAME>: 258.00num| (58.00num above the threshold) \n| BUS: 258.00num| (58.00num above the threshold)
          | Measure|ThreadPoolRuntime-ExecuteThreadTotalCount - teste jira|
          | Affected Server| BUS|
          | Critical Threshold| 200.00num|
          | Warning Threshold| -| \n| <SERVERNAME>: 258.00num| (58.00num above the threshold) \n| BUS: 258.00num| (58.00num above the threshold)
          2016-01-29 21:14:06 INFO [CreateIssueActionPlugin@com.dynatrace.diagnostics.jira.CreateIssueActionPlugin.action] Custom field : customfield_10024=10003

  16. Anonymous (login to see details)

    Hi Team, 

     

    I'd tried to use the latest JIRA plugin version, however I can't see the issue created in the Jira. In the system information there are some incidents created using JIRA action but these aren't created in the ticket system. Could you please help me on it? 

     

    Thanks in advance, 

     

    Regards,

     

    Monica

    1. Anonymous (login to see details)

      Hi Monica

      Action Plugins are invoked on the Dynatrace Server. In case something goes wrong, e.g: plugin cant reach JIRA Server or authentication failed an indication of this error should show up in the dynatrace server log files. Can you look there and see whether you can find anything?

      Andi

  17. Anonymous (login to see details)

    Hi Andi,

     

    Thanks for your response. Actually the integration is working well. The Issue type was different and now it works.

     

    Thanks and Regards, 

     

    Monica

  18. Anonymous (login to see details)

    Does this support CA Spectrum ticketing or Remedy ticketing systems? Is it able to send out customized SNMP traps?

  19. Anonymous (login to see details)

    Hi,

    the pugin uses the JIRA Java client library, so it's very specific.

    If Spectrum an Remedy provide the same kind of java client library, it should be failry easy to adapt...

  20. Anonymous (login to see details)

    Hi Laurent & Team.,

    I tried installing the Jira Action Plugin in our environment - It did work as expected. Unfortunately - I do not see any option to set the Environment field in Jira with the Current plugin (0.0.10) Jira Version 6.2

    Appreciate if anyone could share me the latest release which has Environment field.

    Many thanks

    Best regards

    Kiran Yolarotti

  21. Anonymous (login to see details)

    Hello,
    we are extending JIRA plugin for dynatrace. We are trying to link incident with purepaths in any way, but Incident.getPurePaths() returns empty list. According to information I have found over internet, you doesn't support this method any more. Is there any way to generate from provided information uri which will open at least web client on proper dashboard? It would improve workflow with JIRA task for our client.

    Another option which would be enough for us is getting affected Agent and Application names.

    One of such incident we need to describe is "Failure rate to high". Can you show use correct path to obtain what we need?

    Best,
    Sebastian