New Relic announced a new integration with Atlassian.
New Relic is integrated into Atlassian’s new capability to track incidents in Jira Software. The integration empowers engineering teams to bolster their incident management and resolution practices with insights gained from software issues detected in New Relic. This enables organizations to more effectively manage current incidents and prevent future ones, freeing more time for product innovation.
The Incidents tab in Jira sends incidents from New Relic and other tools to Jira, allowing teams to quickly learn about the incident and focus on identifying the affected services, entities, and issues. By surfacing post-incident reviews (PIRs) in Jira, teams can assign and manage preventative work to reduce the frequency and volume of costly incidents. New Relic is the first and only observability provider to offer an integration available in early access to Jira customers, which helped shape Jira's new capability.
“At New Relic, we believe in meeting engineers where they are, enabling them to do their best work with their preferred tools. We are delighted to be the first observability platform to integrate with the incidents tab in Jira,” said New Relic Chief Design and Strategy Officer Peter Pezaris. “With our natively-connected solution, we hope to expand access to observability by bringing the right insights into engineers’ existing workflows, helping them manage their work more effectively with the best-of-breed tools they use every day.”
Key benefits of the integration include:
- Enhance incident detection and visibility: Enable development teams to monitor their code’s performance in production and identify associated issues in Jira Software.
- Avoid screen swivel, speed up resolution: Link and create Jira issues with pre-populated incident details from New Relic to help resolve critical issues faster and reduce downtime.
- Prioritize and streamline workflows: Review incidents by priority, affected service, and status to quickly identify incidents that require a team’s attention.
- Establish proactive practices: Create PIRs that include real-time New Relic data to help teams understand root causes, remediation options, and how to prevent recurring incidents.
“We’re on a mission to bring software development and IT operations teams closer together so they can deliver consistently high performing software to their customers,” said Suzie Prince, Head of Product, DevOps, Atlassian. “The New Relic integration automatically surfaces insights and observability data in the new Incidents tab in Jira to further improve collaboration between teams. This can help teams move quickly on active incidents and take action to prevent recurring incidents.”
The New Relic integration for the Jira Incidents tab is the latest collaboration between New Relic and Atlassian. It builds on the recent New Relic errors inbox integration with Jira for error tracking, the Bitbucket quickstart in New Relic Instant Observability to monitor and optimize deployments, and New Relic alerts integration with Jira to help the right teams get the right information in the software development lifecycle.
The Incidents tab in Jira is currently available in early access.
The Latest
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.