Jira Connector.

A site finding becomes an issue in Jira. Protuno can then move it to another status as the fix is verified. Writes ask you first by default.

WorkDocumented by AtlassianConnectable
  • API token
Run Free AuditOpen Jira (opens in a new tab)

No install needed for the audit. We suggest connecting a staging copy of your site first, before your live site.

Protuno connects to Jira. 2 reads, 2 writes.
2 on its own · 2 ask first

Permissions.

Reads can run on their own. Writes ask you first by default.

Reads

2 reads

Projects and issue search.

  • List projects
  • Search issues (JQL)
Writes

2 writes

Create an issue and move its status. Both ask first by default.

  • Create an issue
  • Move an issue to another status
All 4 capabilities

Showing 4 of 4 capabilities

Read

  • List projectsjira.project.read

    Lists the projects the account can see, so Protuno knows where an issue belongs.

    On its own

  • Search issues (JQL)jira.issue.search

    Searches for issues with a JQL query, to find one that matches a finding.

    On its own

Write

  • Create an issuejira.issue.create

    Creates a new issue in a project, one issue per finding.

    Undo: Move the issue to a closed or cancelled status. Jira has no safe reverse of create.

    Ask first

  • Move an issue to another statusjira.issue.transition

    Moves an issue to a new workflow status, only after the fix is verified.

    Undo: Read the issue's prior status first, then move it back to that status.

    Ask first
What It Does

Findings Become Jira Issues You Can Track.

Protuno can turn a site finding into a Jira issue, and move it to another status as the fix lands. Every write asks first by default.

Search issues (JQL)

Searches issues with a JQL query, so Protuno does not file a duplicate for something already tracked.

Reads

List projects

Lists the projects the account can see, so Protuno knows where a new issue belongs.

Reads

Create issue from finding

Creates a new issue describing one finding, for example a plugin stuck mid-update.

Ask first

Move an issue

Moves an issue to another status once Protuno has verified the fix worked.

Ask first

Playbooks none yet

No playbook reads it yet. This is where a finding becomes a ticket.

Set Up · 5 steps

You See The Full List Before Anything Is Granted.

How it connects: you create an Atlassian API token and paste it into Protuno with your Jira site address and your Atlassian account email. Protuno works with Atlassian Cloud sites only, for example yourname.atlassian.net. The token acts with the permissions of the account that created it.

  1. Step 1

    Create an API token

    Go to id.atlassian.com/manage-profile/security/api-tokens, choose Create API token, name it and set an expiry.

    Copy the token when Atlassian shows it.

    you see: A token shown once on Atlassian's own page, with the expiry you set.

  2. Step 2

    Paste the site, email and token

    Choose Jira in Protuno's connector list.

    Paste your Jira site address, your Atlassian account email and the API token.

    you see: Three fields (site, email, token) and a Connect button.

  3. Step 3

    See what it can do

    Protuno asks Jira what the account can reach and shows reads on the left and writes on the right.

    you see: Reads on the left and writes on the right: listing projects and searching issues on the left, and creating an issue and moving its status on the right.

  4. Step 4

    Choose what runs

    Reads run on their own.

    Writes ask you first by default.

    you see: A control for each capability, with writes set to ask first.

  5. Step 5

    Confirm what you grant

    Confirm    Protuno replays the grant as one sentence and you agree to it.

    you see: A plain sentence summing up exactly what was granted, an Agree button and a confirmation screen.

Before You Connect It

Questions.

What Jira plan or tier does Protuno need?

Atlassian's docs do not name a paid-plan requirement for API access. Access follows the permissions of the account that created the token.

What are Jira's API rate limits?

Atlassian applies three limits at once: an hourly quota of points (reads and writes cost points), a per-second burst limit on each endpoint, and a cap on how often one issue can be changed. Go over any of them and Jira returns an HTTP 429 error. Atlassian's rate limiting page has the current numbers.

What can't Protuno do in Jira?

It cannot delete issues, administer projects or permissions, or look up users. It creates issues and moves their status, and both ask you first by default.

How fresh is the data Protuno sees?

Protuno reads issues live from the Jira REST API v3 each time a playbook runs. There is no cached copy. The finding itself is written into an issue, and the raw payload from Jira is not stored.

An issue Protuno created is not showing up. What is wrong?

Confirm the issue was created in the project you expect. Jira only writes to the project named in the request. Also check that the account that created the token still has access to that site and project.

How do I revoke Jira access?

In Atlassian, open id.atlassian.com/manage-profile/security/api-tokens and delete the token. Disconnecting in Protuno does not revoke the key at Atlassian. Delete it there to cut access for good.

Capability names and default settings (on its own or ask first) are Protuno's own, and they can change as the product develops. Playbook plan, schedule and date come from Protuno's agent pages. Protuno last confirmed this connector's build status on 13 Oct 2026. Vendor limits and permissions on this page follow the vendor's public documentation as reviewed on 13 Oct 2026. The vendor's own page is the final word.

Free Site Audit

Do You Use Jira?

The free audit looks at the site from the outside. Connect tools afterwards, one capability at a time.

We suggest connecting a staging copy of your site first, before your live site.

85 Site ChecksNo Credit Card100% Free