Assigning Tickets from one Customer Organization to Another.

AS_4u0iki

@Mike Bowen I have read through some of your postings and the information is great stuff. Thank You! 

I have received a request to have the tickets in the JSM be separated by dept where the tickets can not be viewed across due to PPI or MAC Address' etc. I figured creating Customer Based Organizations for our internal departments would be the best way to do this. 

The issue that I am running into is when departments need to cross functionally support each other. Example, When Development needs Infrastructure to support one of their tickets, they are unable to assign across Organizations. 

Attached are the customer permissions, my original thought was to allow customer sharing for other customers within their project or organization -- to allow cross-customer org collaboration. 

I am also working in our Sandbox environment, if that helps.

 

 

Brant Schroeder

@AS 

An issue can only have a single organization associated with it.  This allows others in the organization to see the issue in the customer portal.  If there are others that need to see the issue outside of that organization in the customer portal they will just need to be added as a request participant.  If the additional organization has 6 people in it they would all need to be added as request participants if you would like to see the issue and communicate on it as a customer.