New Relic customers using JIRA 7—the latest version of Atlassian’s popular issue- and project-tracking software for agile teams—need an easy way to integrate their JIRA instance with New Relic.

Our new JIRA 7 integration—now generally available—is designed to address these needs with deep integration between New Relic APM and Atlassian JIRA. The integration is intended to give our customers using the latest version of JIRA the capability to create and track JIRA issues with the contextual, temporal information needed to quickly and effectively fix the issues, along with deep links back to APM that bring up the exact context where the issue was created.

Completing the DevOps feedback cycle

Critically, JIRA 7 integration helps complete the DevOps feedback cycle in New Relic APM, giving teams a unified view of their entire software development project. The seamless inclusion of JIRA 7 data in your APM interface lets you easily file issues to the responsible teams for tracking—automatically including the context they need to resolve the issue.

Specifically, you can now correlate production incidents with JIRA tickets. You can automatically correlate incidents detected by New Relic with JIRA tickets. And you can always see the current status and severity of an incident directly from within a correlated JIRA ticket.

New Relic APM JIRA 7 integration screenshot

[click to enlarge]

file a apm jira 7 ticket example

Improving JIRA 7 issue creation

Our priority for JIRA 7 integration centered on the issue-creation process. When you discover problems in your application using New Relic that you need your developers to fix, you can push the details directly into your ticketing system in your JIRA 7 Server account. We built our integration to work with any combination of required custom fields.

Successful integration with JIRA 7 Oauth1a was key to ensuring that our customers can access this process. OAuth is used for server-to-server authentication in JIRA, especially behind firewall applications. It’s the authentication protocol that allows users to grant a third-party application access to their information on another site.

The New Relic JIRA 7 integration is designed to let customers correlate potential root causes for incidents between the two programs. We believe general availability of the integration will greatly improve troubleshooting of production incidents across multiple teams by automatically correlating information all the way down to the individual line of code that caused the issue in the first place.

Learn more about working with JIRA 7 in New Relic by checking out the documentation and joining the discussion about New Relic JIRA Integration in the New Relic Online Technical Community.

 

Shreyans Parekh is a Product Marketing Manager at New Relic, where his job is to focus on market and industry dynamics in the areas of cloud migration and DevOps. His writing has appeared in publications by Internet Retailer, Intuit, Apttus and IBM Bluewolf. He can be reached on Twitter @ShreyParekh. View posts by .

Interested in writing for New Relic Blog? Send us a pitch!