Automation didn't work using "Run as the user who triggered the rule" options
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Admin set automations configurations options as "Run as the user who triggered the rule" for customer user conditions.
When making the following configurations for Automations and the options is set as "Run as the user who triggered the rule" :-
- Issue is not transitions when issues matches the status and user is a customer.
Diagnosis
Environment
- JIRA 6.4.3
- JSD 2.5.9
Cause
The project workflows configurations for the transitions , had settings for Conditions . For example below screenshots :-
By doing this , Customer user can't transitions the issue . Because by default , Customer is not in both group .
So , to let Customer user transitions issue , Conditions configurations must not prevent them from performing transitions.
Resolution
There's 2 options to fix this problem :-
Option 1
- Remove conditions configurations in the project workflow . If the conditions is required , then need to make sure Customer user is meeting the conditions.
Option 2
- Set Automations options to Run as project default
- Make sure the User is meeting the workflows conditions.