When choosing a user account to run a post function, the specified user account specified must have the appropriate permissions to perform the actions of the post function, for example, , such as creating an issue or adding a comment.
| Info |
|---|
If JSU determines that the specified user has insufficient permissions, it executes the rule using the JSU Add-on user. This is displayed in the Execution Log as a success and includes a warning. JSU can’t determine if the specified user is missing necessary Jira global permissions. In this case, the rule runs using the specified user. If the run encounters a Jira error, it will fail. This is displayed in the Execution Log with a permission error. |
...
JSU Add-On User (default): The JSU Add-On User account is automatically added to an instance automatically when JSU is installed and already has the required permissions to perform all actions across JSU Post Functions. As long as post functions. If the permissions haven’t been manually removed from the JSU Add-On User, there it should be no impact to it being the “Perform as User” not impact its success as the Perform as User instead of another account.
...
Choose User: Use this option to specify a different user account that has been granted the necessary permissions. Usually, this user account is assumed to be only technical (impersonation), with broad permissions, and not used for logging by individuals to log into Jira by coworkers.
In combination with the Permission Condition in native Jira, or the User Is In Any Users Condition from JSU, you can hide a transition from all users that do not have permission to execute it.
...