Issue Summary

When a customer is added to a new JSD organization that does not match the customer domain and then removed after that all customers with the same domain name are added to the JSD org by Automation for Jira to which the above user was added even though there is no mapping
This is reproducible on Data Center: (yes)

Steps to Reproduce

• Go to any existing organization (testdomain.com.au) within JSM and add a customer with a different mail domain(user@example.com)
• Create automation rule as below to add customers to an organization depending on the email domain name
  
• Remove the user from the organization
• Then, when the user is removed: write a mail from exactly that domain (another-user1@example.com) to JSM

Expected Results

The customer user1@example.com either would be added to the new organization example.com if the Automation rule has the option to create a new organization if not found or else this user will not be added to any organization.

Actual Results

The customer user1@example.com is added to the same random organization testdomain.com.au where the customer with the same domain name was added earlier and later deleted.

Workaround

No workarounds currently available