Hi
While recently cleaning up some project settings in a Service project, we noticed under Customers it was listing an Organisation called "Deleted". It contained a list of customers from our own Jira users and guests.
We weren't sure if someone had manually added this Organisation, but as we have now also discovered it exists in all of our other Service projects, including two relatively new ones, it seems to be made by the system?
Wondering if someone can clarify:
We were mainly worried about accidental data sharing of tickets between unrelated customers in the "Deleted" Org. Some initial testing seems to indicate we should be fine as long as there are no email domains associated with the org?
HI @Allan Sanderson ,
Hope this documentation helps. It basically use to make it easier to apply user with certain email domains to your service desk projects without adding them manually one by one.
Thanks @Benjamin
Yes, I am already using email domains to automatically group customers into organizations, and have configured an automation to do this on issue creation. This part is all working well.
My question is about an organization that appeared in all of my service projects called "Deleted".
This organization does not have any emails domains associated with it, so new customers will not be added to it automatically.
It also appears to only contain internal Jira users and Jira guests, not external customers.
I want to know if this is a built in system organization? If so, what its purpose is, and is there is any implications in removing it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
addtioanl info to Al's message above.
We have removed all customers from the Organization in all serivce projects and deleted the "Deleted" organization.
the organisation gets recreated automatically by the system after we do this.
customers are addred to the organisation but we don't know why or how.
it does include external users sometimes, we haven't noticed a pattern to it as yet.
This is resulting in ticket information being potentially shared in the portal with people it should not be shared with, because they are auto added to the org....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.