Integrate JIRA issue tracking with your Dynatrace environment

The latest Dynatrace release introduces integration support for Atlassian JIRA. With Dynatrace JIRA integration, issue tickets are generated automatically for all new problems that are auto-detected in your Dynatrace environments.

Atlassian JIRA

Atlassian JIRA is the most popular issue tracking system available today. A high percentage of development and operations departments worldwide use JIRA for issue management. The ability of JIRA to manage issues, trigger workflows, and track code and production changes is crucial for modern DevOps departments.

Easy, direct integration of Dynatrace and Atlassian JIRA saves you a lot of manual work and completely automates the reporting of Dynatrace detected problems in your monitored environment into your organization’s JIRA project.

Configure JIRA integration

To configure JIRA integration with Dynatrace

  1. Go to Settings Integration Problem notifications.
  2. Select JIRA from the list of 3rd party systems.
    Atlassian JIRA
  3. Type a Name for this integration.
  4. Type in your JIRA endpoint URL.
  5. Type in the corresponding Username and Password for this JIRA project.
  6. Type in the JIRA Project key (not the project name) of the JIRA project where new issues are to be created and tracked. To find all available project keys, within JIRA, go to Projects > View all projects.
  7. Type in the JIRA Issue type that should be used for issues detected by Dynatrace.
    Note: You must specify an issue type that’s already been set up in JIRA. Otherwise, the integration will fail. To find all available issue types, or to create a new issue type, within JIRA go to Options > Issues.
  8. Type a brief Summary of the issue. You can type text and/or insert placeholders (see Available placeholders below) that will automatically be populated with relevant problem details, such as problem ID, state, or impact.
  9. Type a more detailed Issue description for the issue. You can type text and/or insert placeholders (see Available placeholders below) that will automatically be populated with relevant problem details, such as problem ID, state, or impact.
  10. Click the Send test notification button to confirm that your JIRA Dynatrace integration is working.
  11. Click Save.

Placeholders for JIRA Summary and Issue description

  • {State}: Problem state. Possible values are OPEN and RESOLVED.
  • {ProblemID}: ID number of the reported problem.
  • {PID}: A unique system identifier for the reported problem.
  • {ProblemImpact}: Impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE.
  • {ProblemTitle}: A short description of the problem.
  • {ImpactedEntity}: Entities impacted by the problem (or the term “multiple” when more than two entities are impacted).
  • {Tags}: Comma-separated list of tags that that have been defined for all impacted entities.

Once saved, the integration appears in your list of third-party integrations, as shown below.

Atlassian JIRA

With your JIRA integration complete, JIRA tickets are now automatically created within your JIRA project for all Dynatrace auto-detected problems, as shown below.

Atlassian JIRA

Automatic severity updates

Keep in mind that Dynatrace automatically updates the severity levels of issues in JIRA based on their impact to your applications and customer experience. Resolved issues are however not closed automatically. JIRA issues must be closed manually.

What’s next

This initial Dynatrace JIRA integration represents only a first step toward a planned two-way integration of JIRA workflows and Dynatrace. We’re working on additional integration features in close cooperation with our partners at Atlassian, so please stay tuned. One upcoming enhancement to look forward to is automated creation of problem comments and linking from Dynatrace directly to related JIRA issues.

Wolfgang is a Technical Product Manager at Dynatrace. He has a long record of research in software analytics and mobile computing. At Dynatrace, he's responsible for baseline calculation and event correlation in performance analytics. He also drives the topic of mobile app monitoring.

Looking for answers?

Start a new discussion or ask for help in our Q&A forum.

Go to forum