...
Warning |
---|
title | Create at least one JIRA Project |
---|
|
In order for the JMWE add-on to work properly, you need to have created your first Jira Project. If you haven't, most configuration pages will not work, and you will see security-errors in your logs. |
Anchor |
---|
| globalpermissions |
---|
| globalpermissions |
---|
|
1 - Check your Global permissionsVerify that the atlassian-addons-admin
group has the Jira Administrators permission, and that the Jira Misc Workflow Extensions
user belongs to that group.
Panel |
---|
Steps: - Go to the Global permissions page (type gg then Global permissions)
- Check whether the
atlassian-addons-admin group belongs to the Jira Administrators permission. - Click on the View Users link below the
atlassian-addons-admin group and verify that the Jira Misc Workflow Extensions user belongs to that group. - If either of these checks fail, your Jira instance is not properly configured. You need to uninstall and then reinstall the JMWE add-on and check again. If the checks still fail, you need to contact Atlassian Support and ask them to fix these issues.
|
2 - Make sure the "Jira Misc Workflow Extensions" user has access to all applications and belongs to the appropriate groupsYou need to ensure that the Jira Misc Workflow Extensions
user has access to all Jira applications, and belongs to the corresponding groups : jira-core-users, jira-servicedesk-users
and jira-software-users
(depending on the Applications you have activated). If not, select the missing applications.
Panel |
---|
Steps: - Go to the User Management page (type gg then User Management).
- Click on the Active users popup menu and select "System Users"
- Click on the
Jira Misc Workflow Extensions user to edit it - Under Application access, select (check) all Jira applications
- Verify that the user belongs at least to these groups:
jira-core-users jira-servicedesk-users (if you are running Jira Service Desk)
jira-software-users (if you are running Jira Software)
- If not, add the user to the groups, using the Add group link.
|
Anchor |
---|
| permissionschemes |
---|
| permissionschemes |
---|
|
3 - Check your Permission schemes
For each permission scheme, make sure all permissions are granted to the atlassian-addons-project-access
project role in the Permission Scheme of the project.
Panel |
---|
Steps: - Go to the Permission Schemes administration page (type gg then Permission Schemes)
- Click on the first Permission Scheme
- Make sure that the
atlassian-addons-project-access project role is granted all permissions. If not, grant the missing permissions to that project role. - Repeat with all other Permission Schemes.
|
4 - Make sure that the "Jira Misc Workflow Extensions" user belongs to the atlassian-addons-project-access project role of every project
You need to ensure that the Jira Misc Workflow Extensions
user belongs to the atlassian-addons-project-access
project role of every project. If not, add the user to the project role, using Add users to a role link
Panel |
---|
Steps: - Go to the Projects page (type gg then Projects)
- Locate your project and select User and roles.
- Verify that the user
Misc Workflow Extensions for Jira Cloud belongs to the atlassian-addons-project-access project role. - If not, add the user to the project role, using Add users to a role link.
|
Anchor |
---|
| issuesecurityschemes |
---|
| issuesecurityschemes |
---|
|
5 - Check your Issue Security schemesFor each Issue Security scheme, make sure that the atlassian-addons-project-access
project role belongs to every Security Level.
Panel |
---|
Steps: - Go to the Issue Security Schemes administration page (type gg then Issue Security)
- Click on the first Issue Security Scheme
- Make sure that the
atlassian-addons-project-access project role belongs to each Security Level. If not, use the Add link to add the atlassian-addons-project-access project role to each security level. - Repeat with all other Issue Security Schemes.
|
Anchor |
---|
| workflowstepproperties |
---|
| workflowstepproperties |
---|
|
6 - If you are using jira.permission.* workflow step properties
You need to add the atlassian-addons-project-access
project role to the jira.permission.*
property value
...