We have a customer with its email added to two different organizations, for sake of e.g. we call them OrgA and Org B
What we did, is to remove the email from OrgB, because we do not want this customer to be creating service tickets attached to OrgB.
We then asked that customer to send email to support channel in order to open a test ticket.
We expected to see new ticket to be in OrgA only.
Ticket got opened in OrgB and customer got automatically added to Org B.
Why is this happening despite us removing the customer from OrgB?
The only workaround we could come to is to delete the entire Org and recreate without that customer in that org - this is not an acceptable way to handle this when there is an option to remove the customer from an org
Are all the users are able to see the ticket or just the one who created the ticket?
The one who created the ticket should be able to see the ticket, even though you have removed customers from an org.
For this to change you need to modify corresponding customer permissions.
Hi @Sushant Pandey, this is odd. Organizations don't get assigned automatically by default—unless your global configuration is set to "new requests automatically be shared with a customer's organization," but even though it shouldn't assign to an organization the customer doesn't belong to. I've seen a similar scenario where automation assigned organizations based on the email domain. Have you checked if any automation could be assigning it to the ticket?
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events