What Permissions are Required for Jira Users?

Connecting Jira to Unito is quick and easy with OAuth2. Other methods, however, require specific permissions. Below are several options and what's needed for each.

In this article:

Unito can only perform the same actions as the user who connects it to their Jira account.  So in order for your Unito flow to create an issue or task, change a status, or leave a comment, you must have permission to perform that action too.

General Jira Permissions

In general, you must be able to:

  • Login to Jira
  • Browse users and groups (Required for managing assignees, reporters, and commenters involved in your Unito workflows)

If you're connecting via OAuth2, then your workspace members don't require specific permissions to create a Unito flow.

Details on how to set permissions in Jira can be found in the Atlassian Jira Knowledge Base, and information about managing permissions can be found here.

Here's our step-by-step guide on how to configure Unito for Jira access.


Authorization Methods

OAuth2 is the most secure and reliable method of connecting Jira to Unito. It allows for granular control over permissions and simplifies setup without requiring high-level admin access. We recommend using OAuth2 for connecting your cloud-based Jira accounts.

Jira Cloud OAuth2

Other methods

There are other authorization methods for connecting Jira to Unito, but they require additional steps and permissions in order to sync properly with Unito:

  • API Key: Requires certain Jira administration permissions to create the key.
  • OAuth1: May have limitations for some actions and generally requires a Jira administrator.
  • Username and Password: Least secure method and often requires Jira administrator permissions. 

Important: If possible, create a Jira service account (also known as a bot user), for the Unito integration. This improves security and makes managing the integration easier.

Permissions required to sync with Jira

Global Jira permissions

  • Login to Jira
  • Browse Projects
  • Administer Projects

Why do we need these?

  • These permissions are necessary for Unito to communicate with Jira and perform actions like creating issues, making updates, and adding comments.
  • Using webhooks (enabled by these permissions) allows for smoother and more efficient synchronization between Jira and your other connected tools.

The following permissions are needed if you want to have webhooks enabled. If not, you can still sync with Unito, but your flow won’t update issues in real-time.

Project permissions

Issue permissions
  • View Development Tools

  • View Read-Only Workflow

  • Assignable User
  • Assign Issues
  • Close Issues
  • Create Issues
  • Edit Issues
  • Assignable User
  • Assign Issues
  • Close Issues
  • Create Issues
  • Edit Issues
  • Link Issues
  • Modify Reporter
  • Move Issues
  • Resolve Issues
  • Schedule Issues
  • Transition Issues 

Comments permissions

Time tracking permissions
  • Add Comments
  • Edit All Comments (if you want to allow Unito to edit comments)
  • Edit Own Comments
  • Work On Issues
  • Edit All Worklogs
  • Edit Own Worklogs 

Attachments permissions

Voters & watchers permissions

  • Create Attachments (if you want Unito to be able to attach files to issues)
  • View Voters and Watchers (if you want Unito to keep track of voters and watchers on Jira issues)