-
Changes made by post-functions are not always visible immediately —
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
-
Comment Issue and Comment Linked Issues post-functions do not support 'Send "Issue commented" notification' option —
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. -
Create transition fails when post-functions are placed inappropriately —
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
-
JMWE for JIRA Cloud doesn't work after migrating from one JIRA Cloud instance to another —
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.
-
Limited support for Internet Explorer 11 —
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 fail to modify Service Desk issues —
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. -
Permission errors while executing post-functions —
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
-
Post-functions fail with a security error if the add-on user does not belong to the Issue security schemes of the project —
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.
-
Post-functions seem to be running in no apparent order —
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 transition an issue fail when their position on a transition is inappropriate —
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.
If one of the post-functions provided by the add-on does not seem to be working as you would expect, you might want to know whether you are running into a known issue. This document lists them.
On this page:
General known issues
The following list of issues are identified as general known issues.
Connect post-functions changes are not always visible immediately
Issue : Changes made by the Connect post-functions are not always visible just after the post-function execution, which will be alarming to the users. This is because JMWE's new post functions are processed remotely and updated. This helps ensure the stability and performance of your JIRA instance.
Workaround : Refresh the page to see the changes done by the post-function.
Cannot rely on post-function sequence for Connect post-functions
Issue : Due to the asynchronous nature of the Connect post-functions in JIRA Cloud, it is not possible to guarantee the order in which post functions would be executed. This will break the workflows that depend on post functions being executed in a specific order.
Workaround : None
See also : SJMWE-202
Post-functions with issue links are unreliable on the Create transition
Issue : Using JMWE post-functions that depend on issue links (all links including parent/sub-task and Epic/Story) in the Create transition is unreliable. Consequently, such workflows will work unreliably. This is because the link might not yet be created when the post-function runs.
See also : ACJIRA-962
Post-functions fail when their position on the Create transition is inappropriate
Issue : When a post-function is placed at the top of the list of post-functions on the Create transition, it will fail and throw an error. This is because the post-function performs an action even before the issue is created.
Workaround : You need to place any JMWE post-function after the Creates the issue originally built-in post-function.
Post-functions that transition an issue fail when their position on a transition is inappropriate
Issue : 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.
Workaround : You need to place these post-functions at the end of the list of post-functions.
Known issues specific to migration
The following list of issues is informative to customers migrating from the P2 version of JMWE to the Connect version.
Most Post-functions cannot work on Service Desk issues
Issue : Most of the post-functions cannot work on the Service Desk projects issues. This is because JIRA returns a 403 (You do not have the permission to see the specified issue
) error for the add-on user. Therefore, workflows that work on Service Desk projects will break.
Workaround : Manually fix Permission Scheme for the Service Desk projects. See here to know how to fix it.
Post-functions fail with a security error if the add-on user does not belong to the Issue security schemes of the project
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.
Workaround : Manually add the add-on user to each security level of every Issue security scheme. See here to know how to fix it.
See also : ACJIRA-983
Assign to [last] role member post-functions do not support skipIfAssignee, useSelectedUser and forceSelectedUser options
Issue : The post-functions Assign to last role member and Assign to role member don't support skipIfAssignee, useSelectedUser and forceSelectedUser options. Therefore, workflows using these options won't work as before.
Workaround : None
Most post-functions are now executed as the add-on user instead of the current user
Issue : Most post-functions now operate as add-on user instead of the current user to ensure security. Therefore, updates may appear to be done by the JMWE add-on user rather than the user who transitioned the issue, thereby changing the Issue history and notification author.
Workaround : None
Copy value from field to field post-function doesn't support using former value
Issue : The post-function Copy value from field to field of the Connect add-on will not support using 'Use value before current transition' option. Therefore, workflows using this option won't work as before.
Workaround : None
Post-functions will fail for workflow steps with jira.issue.editable property value false
Issue : Post-functions on transitions that lead to a status having the property jira.issue.editable
set to false
will fail. This is because the changes will be attempted after the transition is done and the issue has reached its destination status.
Workaround : Manually delete the jira.issue.editable property. See here to know how to delete it.
Comment Issue and Comment Linked Issues post-functions do not support 'Send "Issue commented" notification' option
Issue : 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.
Workaround : None.