Rules using the new "Run as user" option can trigger rules that don't have the "Allow other rules to trigger" option checked

Description

This is due to not running as the Automation user and so we're no longer able to determine if the web hooks from Jira are the result of a real user or Automation running as a user.

There is a write up on this and possible solutions at https://hello.atlassian.net/wiki/spaces/AUT/pages/805308494/Run%2Bas%2Buser%2BRules%2Btriggering%2Bother%2Brules%2Bissue

There is no current fix/work around other than to not use the feature. The Jira Cloud Ecosystem team might be working on a feature that would allow us to fix this, see https://hello.atlassian.net/wiki/spaces/~669992264/pages/807051571/Jira+webhooks+trace+header+spec

Environment

None

Assignee

Unassigned

Reporter

Simeon Ross

Labels

Links

None

Priority

Medium
Configure