Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Verifying your JIRA instance after installation

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.

Identifying configuration issues

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.

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.

1 - Check your Global permissions

Verify that the atlassian-addons-admin group has the Jira Administrators permission.


  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 and Browse users and groups permissions.

  3. If either of these checks fails, 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 - 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.

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

4 - 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