...
| 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 when JSU is installed and already has the required permissions to perform all actions across JSU post functions. If the permissions haven’t been manually removed from the JSU Add-On User, it should not impact its success as the Perform as User instead of another account.
...
When the JSU Add-On User makes changes to issues, you can see the changes in the Activity section of the issue:
...
Initiating User
...
The transition on the related issue is performed with the same user who triggered this post function on the origin issue. That user must have the necessary permissions on the related issue. In some restrictive setups, a user might not be allowed to perform the action or might not have permission to view the relevant project.
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 by individuals to log into Jira.
In combination with the Permission Conditioncondition in native Jira, or the User Is In Any Users Conditioncondition from JSU, you can hide a transition from all users that do not have permission to execute it.
| Info |
|---|
Initiating/SelectedSpecified UserIf you configure your post function for either the initiating user or a selected user, the relevant issue fields must be included in the associated issue screen. For example, if you create a rule that updates a field in a related issue, the field must be included in the target issue Edit screen. Similarly, if you define a rule that creates a new issue, or copies a field to a new issue, the field must be included in the Create screen. |