New Relic + Jira
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.
Why integrate New Relic and Jira?
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.
Automate & integrate New Relic & Jira
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.
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.
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.
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.
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.
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.
Use case
SLA Breach Escalation from New Relic to Jira
When a New Relic alert indicates that an SLA-critical service has breached agreed response time or availability thresholds, tray.ai escalates directly to a designated Jira project with a blocker-level ticket, assigns the on-call engineer, and attaches SLA compliance data. Every breach gets an auditable record in Jira — useful for customer-facing reporting and for internal accountability conversations that would otherwise rely on memory.
Get started with New Relic & Jira integration today
New Relic & Jira Challenges
What challenges are there when working with New Relic & Jira and how will using Tray.ai help?
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 Can Help:
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 Can Help:
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 Can Help:
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.
Challenge
Keeping Jira Ticket Context Rich Without Overwhelming Engineers
Auto-created Jira tickets from monitoring tools tend to fail in one of two directions: too little diagnostic information to be useful, or a raw JSON dump from the alert payload that nobody reads. Either way, the ticket doesn't actually help the engineer who picks it up.
How Tray.ai Can Help:
tray.ai lets teams select and format exactly which New Relic alert fields appear in the Jira ticket description, using templates that organize content into readable sections — summary, affected service, breached threshold, and relevant dashboard links. The result is a ticket that's immediately useful without burying the engineer in noise.
Challenge
Managing Cross-Team Jira Project Routing at Scale
Large engineering organizations with multiple Jira projects, team-specific workflows, and varied alert ownership face a real problem: New Relic alerts need to reach the right Jira project and assignee automatically, and misconfigured routing means tickets sit unowned in the wrong board for hours.
How Tray.ai Can Help:
tray.ai's dynamic routing logic evaluates New Relic alert metadata — application name, host tags, team ownership labels, cloud account ID — and maps each alert to the correct Jira project and default assignee. Routing rules live centrally in tray.ai, so they can be updated without touching individual alert configurations in New Relic as the organization grows.
Start using our pre-built New Relic & Jira templates today
Start from scratch or use one of our pre-built New Relic & Jira templates to quickly solve your most common use cases.
New Relic & Jira Templates
Find pre-built New Relic & Jira solutions for common use cases
Template
New Relic Alert to Jira Issue Creator
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.
Steps:
- Trigger: New Relic alert violation opens via webhook or polling
- Transform: Map alert payload fields to Jira issue schema including priority, summary, and description
- Action: Create Jira issue in the designated project with pre-populated context and labels
Connectors Used: New Relic, Jira
Template
Jira Issue Resolution to New Relic Incident Closer
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.
Steps:
- Trigger: Jira issue status changes to 'Done' or 'Resolved' via webhook
- Lookup: Retrieve the linked New Relic incident ID stored in the Jira issue custom field
- Action: Call New Relic API to close or acknowledge the associated incident
Connectors Used: Jira, New Relic
Template
New Relic Apdex Degradation to Jira Bug Reporter
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.
Steps:
- Trigger: Scheduled poll detects Apdex score falling below configured threshold in New Relic
- Enrich: Fetch transaction breakdown and historical Apdex data from New Relic API
- Action: Create a high-priority Jira bug ticket with enriched performance data attached
Connectors Used: New Relic, Jira
Template
New Relic Deployment Marker to Jira Version Annotator
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.
Steps:
- Trigger: New Relic deployment marker event detected via API or webhook
- Lookup: Match deployment revision to the corresponding Jira project version
- Action: Annotate Jira version with deployment metadata and conditionally create a regression ticket if alerts fire within the post-deploy window
Connectors Used: New Relic, Jira
Template
New Relic Infrastructure Alert to Jira Ops Ticket Router
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.
Steps:
- Trigger: New Relic Infrastructure alert violation opens with host and environment metadata
- Route: Evaluate host tags and environment labels to determine the correct Jira project and assignee
- Action: Create a Jira ops task with priority, affected hosts listed, and a direct link to the New Relic Infrastructure dashboard
Connectors Used: New Relic, Jira
Template
Post-Incident New Relic to Jira Post-Mortem Epic Builder
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.
Steps:
- Trigger: New Relic incident transitions to closed or resolved state
- Enrich: Fetch incident summary metrics from New Relic including duration, error rate peaks, and affected entities
- Action: Create a Jira epic for post-mortem tracking, link related tickets, and attach the enriched incident summary as a comment or attachment
Connectors Used: New Relic, Jira