| Filter by label (Content by label) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
...
| Filter by label (Content by label) |
|---|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
On this page:
| Table of Contents |
|---|
General known issues
The following list of issues are identified as general known issues.
Connect post-functions changes are not always visible immediately
| Panel |
|---|
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
| Panel |
|---|
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
| Panel |
|---|
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
| Panel |
|---|
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
| Panel |
|---|
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
| Panel |
|---|
Issue : Most of the post-functions cannot work on the Service Desk projects issues. This is because JIRA returns a 403 ( 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
| Panel |
|---|
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
| Panel |
|---|
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
| Panel |
|---|
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
| Panel |
|---|
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
| Panel |
|---|
Issue : Post-functions on transitions that lead to a status having the property 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.
...
|