Issue:

Currently, you can either allow portal-only users to assign an org by selecting their org on the 'share with' drop-down or you can allow them to lock it to 'me only' - some customers need to see the org that is associated with the ticket, but do not want the ticket shared with the entire org. 

While JSDCLOUD-4382 implemented a new option for a default that does not share with the org, it also leaves the organization field unassigned on the ticket. 

Suggested solution:

Add an option to disable organizational sharing, while still allowing the organization to be assigned. 

Workaround:

Create a new custom field at the issue level called 'Agency' (or something similar that represents the org), then create automation rules to auto-assign the 'Agency' based on the email domain - and do not assign the 'organization' field on any tickets (as that will give visibility to all users in the org).

This FR is closely related to https://jira.atlassian.com/browse/JSDCLOUD-13159