AllowNow
How-To Guides/Connect Jira
Jira ~10 minutes, one-time setup

How to Connect Jira to AllowNow

Jira is AllowNow's remediation sink — it closes the loop between a review decision and the person who actions it. When a reviewer approves or revokes access, AllowNow opens a Jira ticket with the user, service, and due date; implementor notes sync across as comments; and when the ticket reaches a done status, AllowNow marks the queue item implemented. Authentication is a simple Jira Cloud API token.

Prerequisites

  • A Jira Cloud site (yoursite.atlassian.net)
  • A Jira account that can create issues in your target project
  • AllowNow owner access — connectors live under Connectors in the sidebar
1

Create a Jira API token

2 minutes

Go to id.atlassian.com → Security → API tokens, click Create API token, give it a label like AllowNow, and copy the token. You'll paste it into AllowNow once — it's then encrypted at rest.

2

Note your site URL, project key and issue type

2 minutes

  • Site URL: your Jira base URL, e.g. https://yoursite.atlassian.net.
  • Project key: the short prefix on issue keys — e.g. issues named OPS-123 mean the project key is OPS. This is where remediation tickets are created.
  • Issue type: a type that exists in that project — Task is the safe default.
3

Connect Jira in AllowNow

2 minutes

In AllowNow: Connectors → Add connector → Jira (remediation sink). Enter the Site URL, your Atlassian account email, the API token, the project key, and issue type, then click Connect & test. The test verifies the credentials and that the project is reachable.

4

Understand the ticket lifecycle

read

Once connected, no further action is needed — it works from your existing review flow:

  • A reviewer approves access → a "Grant access" ticket is opened. A reviewer revokes → a "Revoke access" ticket is opened. One ticket per grant (deduplicated).
  • Each ticket carries the affected user, service, role/level, a 7-day due date, and a link back to the AllowNow review.
  • Implementor notes added in AllowNow are posted as Jira comments.
  • Marking the queue item Implemented or Not required posts a summary comment and transitions the Jira issue to a done status.
  • Conversely, moving the Jira issue to done and clicking Refresh tickets (on the Jira connector card) closes out the AllowNow queue item — so either side can drive completion.
Tip: the ticket link and current status appear on each item in the Implementor queue, so the implementor never has to leave AllowNow to find the work.

Troubleshooting

  • ❌ Ticket doesn't transition to Done

    → The project's workflow needs a transition into a status in the done category from the issue's current status. AllowNow still posts the comment and the reverse refresh keeps working.

  • ❌ 400 on create with a field error

    → The project/issue-type requires a mandatory custom field, or the issue-type name is wrong. Use a type with no required fields (e.g. Task) or adjust the project's field configuration.

  • ❌ 401 / 403

    → The API token or email is wrong, or the account can't create issues in that project.

Close the loop on every access change

AllowNow turns review decisions into tracked, audit-logged remediation work — automatically, in the tools your team already uses.

Get started free