Connectors / Integration
Connect New Relic and Jira to Turn Performance Alerts into Actionable Tickets
Automatically create, update, and resolve Jira issues from New Relic alerts so your engineering teams can respond faster and stop switching tabs.
New Relic + Jira integration
New Relic and Jira do two very different jobs — one watches your applications and infrastructure, the other tracks the work needed to fix them. When they don't talk to each other, engineers end up doing the translation by hand: copying alert details into ticket descriptions, manually setting priorities, and trying to remember which incident maps to which ticket. That's slow, error-prone, and nobody's favorite part of being on-call. Connecting New Relic with Jira on tray.ai puts that loop on autopilot — every performance anomaly gets captured, assigned, and tracked without anyone having to play messenger between two dashboards.
The real cost of keeping New Relic and Jira disconnected isn't the minutes it takes to file a ticket manually — it's the minutes that pass before anyone files it at all. When a New Relic alert fires for a spike in error rates, a degraded Apdex score, or a breached infrastructure threshold, your team shouldn't have to open a second browser tab. Automated workflows turn those alerts into prioritized Jira issues immediately, with the right assignee, severity, and context already filled in. And when that Jira ticket gets resolved, the status flows back to New Relic, closing the incident and giving you cleaner post-mortem data. Development, SRE, and ops teams stay aligned without anyone spending their afternoon playing coordinator.
Automate & integrate New Relic + Jira
Automating New Relic and Jira business processes or integrating data is made easy with Tray.ai.
Use case
Automated Incident Ticket Creation from New Relic Alerts
When a New Relic alerting policy fires — an error rate violation, a response time breach, whatever threshold your team has set — tray.ai creates a Jira issue in the right project without anyone touching a keyboard. The ticket arrives pre-populated with alert details, affected entities, severity level, and a direct link back to the New Relic incident. No lag between detection and acknowledgment, which is usually where incident duration quietly grows.
- Cuts mean time to acknowledge (MTTA) by removing manual ticket creation from the process
- Ensures no alert goes untracked in your project management system
- Pre-populates tickets with diagnostic context so engineers can start triage immediately
Use case
Bi-Directional Incident Status Synchronization
Keep New Relic incident states and Jira issue statuses in sync automatically. When an engineer moves a Jira issue from 'In Progress' to 'Resolved,' tray.ai closes or acknowledges the corresponding New Relic incident, and the reverse works too. Without this, stale open incidents pile up in New Relic and orphaned tickets clutter Jira — both are the kind of noise that makes teams stop trusting their dashboards.
- Eliminates the duplicate work of updating status in two separate tools
- Gives you a single source of truth for incident lifecycle management
- Reduces noise from stale open alerts cluttering dashboards
Use case
Apdex Score Degradation to Jira Bug Workflow
When New Relic detects a sustained Apdex score drop for a specific application or service, tray.ai files a high-priority Jira bug assigned to the responsible team. The ticket includes historical Apdex trend data, the affected transaction names, and a snapshot of relevant New Relic charts as attachments or links. Performance regressions that might otherwise sit invisible in monitoring data become assigned engineering work.
- Turns performance degradation into visible, assigned engineering work
- Attaches quantitative data directly to the ticket for faster root cause analysis
- Surfaces user-experience issues before they escalate into outages
Use case
Infrastructure Alert to Jira Ops Task Automation
New Relic Infrastructure alerts for CPU, memory, disk, or network thresholds can automatically generate Jira tasks in your operations backlog. tray.ai maps alert severity to Jira priority levels and routes tickets to the correct ops team based on the affected host or cloud account. Infrastructure health issues stay visible alongside product work instead of getting lost in a Slack thread.
- Routes infrastructure incidents to the right team without manual triage
- Maintains a traceable audit trail of infrastructure issues in Jira
- Keeps operational work visible alongside feature development in a shared backlog
Use case
Post-Incident Review Automation and Jira Epic Linking
After a New Relic incident closes, tray.ai can trigger a post-incident workflow that creates or updates a Jira epic for post-mortem tracking, linking all related incident tickets under a single parent issue. Relevant New Relic data — alert duration, impacted services, throughput metrics during the incident window — gets attached to the epic automatically. Engineering leaders get a structured, data-backed foundation for every retrospective without someone spending an hour assembling it.
- Automates the administrative setup required for post-mortem meetings
- Centralizes all incident-related tickets under a traceable Jira epic
- Pulls quantitative incident data without requiring engineers to compile reports manually
Use case
Deployment Marker Correlation with Jira Release Tracking
When a new deployment is marked in New Relic, tray.ai cross-references the release with corresponding Jira version records and annotates tickets with deployment timestamps. If a New Relic alert fires shortly after a deployment, the integration links the resulting Jira ticket to the most recent release automatically — so teams can spot regression-causing deployments in seconds rather than piecing together timelines after the fact.
- Correlates production incidents with specific code releases in seconds
- Helps teams identify regression-causing deployments before they affect more users
- Enriches Jira release records with real-time production health signals from New Relic
Challenges Tray.ai solves
Common obstacles when integrating New Relic and Jira — and how Tray.ai handles them.
Challenge
Mapping New Relic Alert Severity to Jira Priority Levels
New Relic uses its own severity vocabulary — critical, warning, and info — while Jira has a configurable priority scheme that varies by team. Without a deliberate mapping layer, automated ticket creation produces incorrectly prioritized issues that either get ignored or trigger unnecessary urgency. Both outcomes erode trust in the automation quickly.
How Tray.ai helps
tray.ai's data transformation tools let teams define precise field mappings between New Relic alert priority values and Jira priority levels. Conditional logic within workflows can account for team-specific Jira configurations, alert policy categories, or custom severity tags, so tickets land at the right priority every time.
Challenge
Avoiding Duplicate Ticket Creation for Recurring Alerts
New Relic can fire multiple alert violations for the same underlying issue — especially for flapping conditions — which floods the Jira backlog with duplicates if not handled. Engineers end up confused about which ticket to work, and post-mortem analysis becomes a mess of near-identical issues.
How Tray.ai helps
tray.ai workflows can run deduplication logic that checks for an existing open Jira ticket linked to the same New Relic alert policy and entity before creating a new one. If a match is found, the workflow adds a comment with the latest alert details to the existing ticket instead, keeping the backlog clean while preserving the full alert history.
Challenge
Handling New Relic Webhook Payload Variability
New Relic alert webhook payloads vary significantly depending on the alert condition type — APM, infrastructure, synthetic, and NRQL-based alerts each produce different payload structures. A rigid integration breaks whenever a new alert type appears, which is a recurring headache for teams maintaining custom-built connections.
How Tray.ai helps
tray.ai's flexible data mapping and conditional branching let a single workflow handle multiple New Relic payload schemas without breaking. Teams can configure branches for each alert condition type and apply the right field extraction logic to each, so new alert types don't require code changes to accommodate.
Templates
Pre-built workflows for New Relic and Jira you can deploy in minutes.
New Relic Alert to Jira Issue Creator
New Relic 
Jira This template monitors New Relic for new alert violations and automatically creates a Jira issue with severity, affected entity, alert policy name, and a direct link to the New Relic incident. Issues are routed to the correct Jira project based on the alert condition category.
Jira Issue Resolution to New Relic Incident Closer
Jira New Relic When a Jira issue linked to a New Relic incident moves to a resolved or done status, this template closes or acknowledges the corresponding New Relic incident, keeping both platforms in sync and cutting down on alert noise.
New Relic Apdex Degradation to Jira Bug Reporter
New Relic Jira This template polls New Relic for Apdex score violations on monitored applications and files a high-priority bug in Jira automatically, attaching the affected transaction list, Apdex score history, and a link to the New Relic APM dashboard for immediate investigation.
New Relic Deployment Marker to Jira Version Annotator
New Relic Jira When a deployment marker is recorded in New Relic, this template finds the matching Jira release version and stamps it with deployment time and revision details. If a new alert fires within a configurable time window after deployment, a linked Jira ticket is created and associated with that release version automatically.
New Relic Infrastructure Alert to Jira Ops Ticket Router
New Relic Jira This template listens for New Relic Infrastructure alerts and routes them to the correct Jira operations project based on host group, cloud provider tag, or environment label. Ticket priority is set automatically based on alert severity and affected host count.
Post-Incident New Relic to Jira Post-Mortem Epic Builder
New Relic Jira After a New Relic incident closes, this template creates a Jira post-mortem epic, links all incident-related Jira tickets as children, and attaches a summary of incident duration, peak error rates, and impacted services pulled from New Relic's incident API.
How Tray.ai makes this work
New Relic + Jira runs on the full Tray.ai platform
Intelligent iPaaS
Integrate and automate across 700+ connectors with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in New Relic and Jira — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose New Relic + Jira actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Ship your New Relic + Jira integration.
We'll walk through the exact integration you're imagining in a tailored demo.