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.
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.
Permisisons required for non-OAuth2 connections
The following permissions are necessary if you're connecting to Unito via API Key, OAuth1, or through an on-premise (server) version of Jira.
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.
Project permissions
-
Browse Projects
-
Administer Projects (Generally only needed when using API Key or Username/Password)
-
View Development Tools
-
View Read-Only Workflow
- Assignable User
- Assign Issues
- Close Issues
- Create Issues
- Edit Issues
- And more... (The full list depends on what actions you intend to include in your Unito workflows)
Issue permissions
- Assignable User
- Assign Issues
- Close Issues
- Create Issues
- Edit Issues
- Link Issues
- Modify Reporter
- Move Issues
- Resolve Issues
- Schedule Issues
- Transition Issues
Comments permissions
- Add Comments
- Edit All Comments (only if you want to allow Unito to edit any comment on issues)
- Edit Own Comments (only if you need Unito to edit comments it originally made)
Attachments permissions
-
Create Attachments (if you want Unito to be able to attach files to issues)
Voters & watchers permissions
- View Voters and Watchers (Needed if you want Unito to keep track of voters and watchers on Jira issues)
Time tracking permissions
- Work On Issues
- Edit All Worklogs
- Edit Own Worklogs
Additional Resources for Jira Users: