Skip to content

Connecting Jira

This guide walks you through connecting Mayo ASPM to your Jira instance so you can push security tickets directly to your team's boards.

Prerequisites

Before you begin, ensure you have:

  • Jira Cloud or Jira Data Center (version 8.0+)
  • Jira admin access (or ask your Jira admin to complete the OAuth step)
  • Mayo ASPM admin or project-admin role

Step 1 — Start the connection

  1. Navigate to Settings > Integrations > Jira.
  2. Click Connect Jira.
  3. Select your Jira deployment type:
    • Jira Cloud — uses OAuth 2.0
    • Jira Data Center — uses application link with RSA keys

One connection per organization

Each Mayo ASPM organization connects to a single Jira instance. All projects within the organization share the same connection.

Step 2 — Authorize Mayo ASPM (Jira Cloud)

  1. Click Authorize with Atlassian.
  2. You will be redirected to Atlassian's consent screen.
  3. Select the Jira site you want to connect.
  4. Review the permissions Mayo ASPM requests:
Permission Why it's needed
Read Jira project data To list available projects and issue types
Create and edit issues To create and update security tickets
Read and write issue comments To add context and sync status changes
Read user data To populate assignee dropdowns
Manage webhooks To receive status-change events for bi-directional sync
  1. Click Accept.
  2. You will be redirected back to Mayo ASPM with a success message.

Step 2 (alt) — Authorize Mayo ASPM (Jira Data Center)

  1. Mayo ASPM will display an RSA public key and a consumer key.
  2. In Jira, go to Administration > Application Links.
  3. Create a new application link with the URL: https://mayoaspm.com.
  4. Configure the Incoming Authentication:
    • Consumer Key: paste from Mayo ASPM
    • Consumer Name: Mayo ASPM
    • Public Key: paste from Mayo ASPM
  5. Back in Mayo ASPM, click Verify Connection.
  6. Authorize the link when Jira prompts you.

Step 3 — Configure project mapping

After authorization, map Mayo ASPM projects to Jira projects:

  1. You will see a table with your Mayo ASPM projects on the left.
  2. For each project, select a Jira project from the dropdown.
  3. Choose the issue type for generated tickets (e.g., Bug, Task, Story).
  4. Optionally set a default assignee or leave it for ownership policies to decide.
Mayo ASPM Project    →    Jira Project    →    Issue Type
─────────────────         ──────────────       ──────────
payments-api              PAY                  Bug
auth-service              AUTH                 Task
mobile-app                MOB                  Bug

Tip

You can change project mappings at any time from Settings > Integrations > Jira > Project Mapping.

Step 4 — Configure field mapping

Mayo ASPM maps finding data to Jira fields. The defaults work for most teams, but you can customize:

Mayo ASPM field Default Jira field Customizable?
Severity Priority Yes — map each severity to a Jira priority
Finding title Summary No
Description Description No
Labels Labels Yes — add custom labels
Assignee Assignee Yes — override with Jira username
Due date Due date Yes — set SLA-based due dates per severity

Step 5 — Test the connection

  1. Click Send Test Ticket.
  2. Mayo ASPM creates a test issue in your selected Jira project.
  3. Verify the ticket appears in Jira with the correct fields.
  4. Delete the test ticket from Jira (or leave it — it's labeled mayo-aspm-test).

Connection verified

If the test ticket appears correctly, your Jira integration is ready. You can now generate tickets from your findings.

Webhook sync (bi-directional)

Mayo ASPM registers a webhook on your Jira instance to receive real-time updates:

  • Ticket closed in Jira — Mayo ASPM marks the finding as Resolved
  • Ticket reopened in Jira — Mayo ASPM marks the finding as Open
  • Comment added in Jira — visible in the Mayo ASPM finding timeline

Warning

If the webhook is deleted from Jira, bi-directional sync will stop. Mayo ASPM checks webhook health daily and will alert you if the webhook is missing.

Troubleshooting

Problem Solution
OAuth redirect fails Ensure pop-ups are allowed for id.atlassian.com
"No Jira projects found" Your Jira user may not have access to any projects
Test ticket not appearing Check the Jira project's workflow allows the default status
Webhook not working Verify the webhook URL is reachable from your Jira instance

For more help, see Integration troubleshooting.

Next steps