For workflow actions, only admin permissions are required.
For Jira search functionality, both admin and user permissions are required.
Permissions
To connect your Atomicwork and Jira accounts, you need:
Atomicwork admin access: You need org admin access in Atomicwork.
Jira admin access: You need admin access in Jira, allowing you to manage permissions and integrate Jira with Atomicwork.
To access the full range of Jira-Atomicwork features, the admin connecting the Jira site must grant the following permissions in Jira:
Permission | Purpose |
offline_access | To allow an application to obtain a refresh token, enabling it to maintain access to the user's resources over an extended period without requiring frequent re-authentication. |
read:me |
|
read:account |
|
manage:jira-configuration | To perform Jira administration actions like creating projects and custom fields, viewing workflows, managing issue link types. |
read:jira-work | To read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs. |
read:jira-user | To view user information that the user has access to, including usernames, email addresses, and avatars. |
write:jira-work | To create and edit issues in Jira, post comments as the user, create worklogs, and delete issues. |
read:epic:jira-software | To read epics and their issues, and search for epics. |
read:issue:jira-software | To read the details of issues, including Agile fields, and their estimations. |
read:sprint:jira-software | To read the details of sprints, their issues, and properties. |
read:project-role:jira | To view project roles. |
manage:jira-project | To create and edit project settings as well as new project-level objects (e.g. versions and components). |
To allow users to access their Jira issues in Atomicwork, we obtain the following permissions in Jira:
Permission | Purpose |
offline_access | To allow an application to obtain a refresh token, enabling it to maintain access to the user's resources over an extended period without requiring frequent re-authentication. |
read:me |
|
read:jira-work | To read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs. |
read:jira-user | To view user information that the user has access to, including usernames, email addresses, and avatars. |
read:account |
|
Setup - Administrator
As an Atomicwork admin, navigate to Settings > App Store > Jira, and click on Connect.
Enter your Jira Cloud Site URL. If not, click on Connect.
Log into your Jira account and click on Accept to grant the required permissions.
Before clicking accept, make sure you pick the right Jira site in the Jira authorization page.
Your Jira site is now integrated with Atomicwork.
Map Jira projects to Atomicwork workspaces
To create and link Jira issues with Atomicwork requests, Atomicwork admins have to map Jira projects to Atomicwork workspaces.
Navigate to Settings > App Store > Jira, and click on Settings.
Scroll to Create Jira issues and link them with Atomicwork requests and click on Manage.
Add the Atomicwork workspace and link the Jira projects that the agents can have access to from that workspace.
Setup - Employee
Every user who wants to access their Jira issues in Atomicwork will be required to individually connect their account.
You can connect your individual Jira account to Atomicwork by asking the Assistant in MS Teams or Slack to access your Jira issues (by posing a question like "show me issues assigned to me").
The Assistant will prompt you to connect your Jira account and guide you through the process. Alternatively,
Navigate to Organization settings in Atomicwork by clicking on your profile.
Click on Connections in the left navigation bar, and select Connect on the Jira card.
You’ll be guided through the same connection process.