Issue Summary

"Form Submitted Trigger" in response to other automations changing JSM Form status to Submitted, even if not allowed to do so.

Steps to Reproduce

Have a JSM Form attached to a specific request type, the create the following rules:

1. Create Rule A – “Change Form Status > Submitted”
   1. Choose any trigger, manual will do
   2. Add a new action:
      • Action: Change form status
      • Form: Select the form used by the request type.
      • New status: Submitted{}
2. Create Rule B – “Form Submitted” trigger
   1. For the Trigger, select Form submitted.
   2. In the trigger configuration:
      1. Select the same form used in Rule 1.
      2. Make sure to uncheck/disable: Check to allow other rule actions to trigger this rule (the option that allows this rule to be triggered by other rules/automation).
   3. Add a simple action to prove the rule fired, (e.g. Add Comment or Log Action)
3. Turn both rules ON and publish them.
4. Create a new request using the request type that has the configured JSM Form.
5. Perform whatever action is needed to trigger Rule A, which will change the Form status into Submitted.

Expected Results

Only Rule A runs, Rule B should not, as the form status change to Submitted was done by another automation rule, and the Form submitted rule has Allow rule trigger disabled (i.e., it should not be triggered by other automations).

Actual Results

Rule B is also triggered, this shows that the Form Submitted trigger is still being fired by form status changes performed by another automation rule, ignoring the “Allow rule trigger” setting

Workaround

Add a Condition to Rule B trigger, i.e. "User Condition - User Who Triggered Event IS Reporter".