> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Set up deployments and incidents using Jira issues

Implement with AI

Send this guide to your coding agent.

Prerequisite: Install Port MCP

The Create & track DORA metrics in Port guide walks you through installing the DORA metrics experience in Port, using GitHub and PagerDuty as the default deployment and incident methods.

This guide assumes you have already completed that setup and shows how to adapt it for Jira users.

By following this guide, you will see how to define deployments and incidents in Port using Jira issues. By the end, you will be able to leverage DORA metrics using Jira, providing accurate deployment and incident insights in Port.

Prerequisites​

To set up Jira issues for DORA metrics in Port, you will need:

Configure your deployments and incidents​

Let's create a Jira incident blueprint and map Jira issues as deployments and incidents for DORA metrics.

Create a Jira incident blueprint​

The parent DORA guide uses pagerdutyIncident for change failure rate and MTTR. When Jira is your incident source, create a dedicated blueprint that exposes the same fields those aggregations need (resolvedAt and recoveryTime in minutes).

  1. Go to the Data model page.

  2. Click + Blueprint.

  3. Click the {...} button in the top right corner, and choose Edit JSON.

  4. Add this JSON schema:

    Jira incident blueprint (click to expand)
    {
    "identifier": "jiraIncident",
    "title": "Jira Incident",
    "icon": "Jira",
    "description": "An incident tracked as a Jira issue for DORA metrics",
    "schema": {
    "properties": {
    "description": {
    "title": "Description",
    "type": "string"
    },
    "incidentUrl": {
    "title": "Incident URL",
    "type": "string",
    "format": "url"
    },
    "createdAt": {
    "title": "Created At",
    "type": "string",
    "format": "date-time"
    },
    "resolvedAt": {
    "title": "Incident Resolution Time",
    "type": "string",
    "format": "date-time",
    "description": "The timestamp when the incident was resolved"
    },
    "recoveryTime": {
    "title": "Time to Recovery",
    "type": "number",
    "description": "The time (in minutes) between the incident being created and resolved"
    }
    },
    "required": []
    },
    "mirrorProperties": {},
    "calculationProperties": {},
    "aggregationProperties": {},
    "relations": {
    "service": {
    "target": "service",
    "title": "Service",
    "many": false,
    "required": false
    }
    }
    }
  5. Click Save.

Point DORA aggregations at Jira

After you create this blueprint, update the change failure rate and MTTR aggregations from the Create & track DORA metrics in Port guide so their target (and any pathFilter fromBlueprint) use jiraIncident instead of pagerdutyIncident.

Map Jira issues as deployments or incidents​

  1. Navigate to Connectors and select your Jira integration.
  2. Add new mappings to ingest Jira issues as deployment or incident entities.
Technical note: mapping deployments and incidents

These mappings ingest Jira issues into the deployment blueprint from the parent DORA guide, and into the jiraIncident blueprint created above. Adjust the JQL issuetype values to match the issue types your organization uses for deployments and incidents.

Deployments using Jira issues:

- kind: issue
selector:
query: 'true'
jql: issuetype = Deployment AND ((statusCategory != Done) OR (created >= -4w) OR (updated >= -4w))
port:
entity:
mappings:
identifier: .key
title: .fields.summary
blueprint: '"deployment"'
properties:
deploymentStatus: if .fields.resolutiondate != null then "Success" else "Failure" end
environment: '"Production"'
createdAt: .fields.resolutiondate

Incidents using Jira issues:

- kind: issue
selector:
query: 'true'
jql: issuetype = Incident AND ((statusCategory != Done) OR (created >= -1w) OR (updated >= -1w))
port:
entity:
mappings:
identifier: .key
title: .fields.summary
blueprint: '"jiraIncident"'
properties:
description: .fields.description.content| .. | objects | select(.type? == "text") | .text
incidentUrl: ( .self | split("/") | .[0:3] | join("/") ) + "/browse/" + .key
createdAt: .fields.created
resolvedAt: .fields.resolutiondate
recoveryTime: >-
if (.fields.resolutiondate != null and .fields.created != null)
then ((.fields.resolutiondate[0:19] + "Z" | fromdateiso8601) -
(.fields.created[0:19] + "Z" | fromdateiso8601)) / 60 else null
end

You can map Jira custom fields to track additional incident information. Here's an example of mapping custom fields for urgency, status, and priority:

urgency: .fields.customfield_00000
status: .fields.customfield_00000
priority: .fields.customfield_00000

After you save the mappings, Port will begin ingesting matching Jira issues as deployments or incidents.

Filtering or tagging (optional)​

You can filter or tag deployments and incidents by project, issue types, statuses, or other criteria.
This can be accomplished by using JQL (Jira Query Language) within your mapping configuration. For additional information, refer to JQL documentation.

Test your configuration​

  • Create or move to done a Jira ticket matching your mappings.
  • In Port, navigate to the corresponding deployment or incident blueprint to verify that the new entity appears correctly.

Next steps​

  • Once your Jira integration data begins populating, view your DORA metrics dashboard to analyze deployment and incident trends.
  • Link deployments and incidents to teams or services for more detailed insights.

Port DORA dashboard with a monthly deployment frequency value of 1.486 and a weekly frequency trend chart from April to April