Known issues (OLD)

Changes made by JMWE post-functions are not always visible just after the post-function execution. This is because JMWE post-functions (as any other post-functions implemented by JIRA Cloud add-ons) are processed asynchronously, after the transition completes. This helps ensure the stability and performance of your JIRA instance.

This problem is tracked by Atlassian at: https://ecosystem.atlassian.net/browse/ACJIRA-1098

Notifications triggered by the post-functions Comment linked issues and Comment Issue cannot be disabled. This is because these post-functions in Connect add-on do not support the option 'Send "Issue commented" notification'. Therefore, workflows using these functions might generate unwanted notifications.

When a post-function is placed at the top of the list of post-functions on the Create transition, issue creation fails and throws an error. This is a consequence of a JIRA Cloud bug: https://ecosystem.atlassian.net/browse/ACJIRA-961

When you migrate from one JIRA Cloud instance to another (using Backup/Restore), most Connect add-ons, such as JMWE for JIRA Cloud, installed in your instance will stop working. If you navigate to a JMWE screen, such as a post-function configuration screen or the Troubleshooting and Support page, you will receive an "Unauthorized" error. This is due to a known JIRA Cloud bug AC-1528.

Atlassian officially retired support for Internet Explorer 11 in Jira Cloud on March 31, 2020. See this Atlassian Blog post for details.

As a result, some JWME workflow extension configuration screens don’t fully work when using Internet Explorer 11.

My post-functions don't seem to be doing anything when operating on JIRA Service Desk issues, and I see 403 You do not have the permission to see the specified issue errors in the logs.

Some of your post-functions do not seem to be working at all, and in the logs (accessible from the Troubleshooting and support for JIRA Misc Workflow Extensions page) you find errors such as unauthorized or You do not have the permission to see the specified issue.

The post-function is operating on;

• a project that has a non-standard Permission Scheme (such as a Service Desk project) or is using a Security Scheme

• an issue that has a security level set or

• a transition that has a workflow property set which restricts the "Run as" user from seeing/editing the issue

If the add-on user does not belong to the Issue Security schemes of your project, the add-on loses access to the project and therefore the post-function will fail with a security error.

I have configured several JMWE post-functions on a single transition, in a specific order, but the post-functions seem to be running in a different order when I trigger the transition.

This can be a problem in certain cases. For example, if one post-function copies the "Affects Version/s" field from the parent issue of the subtask being transitioned, and then a second post-function copies the "Affects Version/s" field of that subtask to the "Fix Version/s" field, it will not work if the execution order of the two post-functions is reversed.

Post-functions that automatically transition issues i.e. the Transition current issue, Transition parent issue and Transition linked issues fail when their position on a transition is inappropriate.