-
Bug
-
Resolution: Answered
-
Low
-
9
-
Minor
-
3
-
Issue Summary
When a user was previously added to an org, but removed later, this Automation rule add them back in, even if the email domain does not match the name of the Organization
Steps to Reproduce
- Add user to Organization A manually, where the name of the org does not match the user's email domain
- Remove the user from Org A
- Create new Automation rule and add Set organization using reporter's email domain action
- Do not select Create organisation if it doesn't exist
** - Enable rule
- Submit a new request to a JSM portal as the user in step1.
- User was added back to Org A.
Expected Results
User is not added to an organization where the name of the org does not match the email domain of the user.
Actual Results
User added to organisation they were previously member of.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- blocks
-
JSDCLOUD-4519 Email domain organization association
- Closed
- relates to
-
JIRAAUTOSERVER-513 When the first added customer is removed from JSD organisation then the A4J feature "add organization using the email domain of the customer" does not work as expected
- Gathering Impact