After successful installation, you need to verify and potentially adjust your Jira instance configuration to avoid errors during the execution of JMWE post-functions. Most of the configuration required to run the JMWE add-on is done automatically, but if you have customized Jira security settings such as Permission Schemes or Issue Security schemes, you might have to make some additional manual changes.

If you have already configured JMWE post-functions in your workflows and they do not seem to be working appropriately, head for the Troubleshooting and Support page inside your Jira instance, wait a few seconds, and check whether an error box appears mentioning Security Errors.


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.


1 - Check your Global permissions

Verify that the atlassian-addons-admin group has the Jira Administrators permission, and that the Jira Misc Workflow Extensions user belongs to that group.

Steps:

  1. Go to the Global permissions page (type gg then Global permissions)
  2. Check whether the atlassian-addons-admin group belongs to the Jira Administrators permission.
  3. Click on the View Users link below the atlassian-addons-admin group and verify that the Jira Misc Workflow Extensions (or addon_com.innovalog.jmwe.jira-misc-workflow-extensions) user belongs to that group.
  4. 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.

The atlassian-addons-admin group is only visible on the Global permissions page, and not on the Groups and Users pages.


2 - Make sure the "Jira Misc Workflow Extensions" user has access to all applications and belongs to the appropriate groups

You 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.

Steps:

  1. Go to the User Management page (type gg then User Management).
  2. Click on the Active users popup menu and select "System Users"
  3. Click on the Jira Misc Workflow Extensions user to edit it
  4. Under Application access, select (check) all Jira applications
  5. Verify that the user belongs at least to these groups:
    1. jira-core-users
    2. jira-servicedesk-users (if you are running Jira Service Desk)
    3. jira-software-users (if you are running Jira Software)
  6. If not, add the user to the groups, using the Add group link.

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.

Steps:

  1. Go to the Permission Schemes administration page (type gg then Permission Schemes)
  2. Click on the first Permission Scheme
  3. Make sure that the atlassian-addons-project-access project role is granted all permissions. If not, grant the missing permissions to that project role.
  4. 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

Steps:

  1. Go to the Projects page (type gg then Projects)
  2. Locate your project and select User and roles.
  3. Verify that the user Misc Workflow Extensions for Jira Cloud belongs to the atlassian-addons-project-access project role.
  4. If not, add the user to the project role, using Add users to a role link.

5 - Check your Issue Security schemes

For each Issue Security scheme, make sure that the atlassian-addons-project-access project role belongs to every Security Level.

Steps:

  1. Go to the Issue Security Schemes administration page (type gg then Issue Security)
  2. Click on the first Issue Security Scheme
  3. 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.
  4. Repeat with all other Issue Security Schemes.

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

Steps:

  1. Go to the Workflows page. (type gg then Workflows)
  2. Edit the workflow which has the workflow step you wish to edit.
  3. Click on View Properties of the workflow step.

  4. If you have a property set up, add another property with the atlassian-addons-project-access project role.

    For example, if you have,

    • jira.permission.comment.group=some-group, add a new property jira.permission.comment.projectrole=xxxxx

    • jira.permission.comment.group=some-group and jira.permission.comment.user=some-user, add a third property: jira.permission.comment.projectrole=xxxxx

    • jira.permission.comment.user.1=user-a and jira.permission.comment.user.2=user-b add a new property jira.permission.comment.projectrole=10000

    • jira.permission.comment.projectrole=10001 add a new property jira.permission.comment.projectrole.2=10000

where xxxxx is the ID (hover on the actions for the project role in the Project role browser page for the ID) of the atlassian-addons-project-accessprojectrole.

See here for the list of jira.permissions.* properties.