Issue Summary

 
When moving a ticket from Project A to Project B within JSM (Jira Service Management) projects, where each project is associated with its own organization, the organization from Project A (Org1) remains attached to the ticket after the move. This creates a potential security concern, as the customer expects that the organization from the originating project should either be automatically removed or a warning should be triggered, prompting the user to remove it manually. This issue could lead to unintended information sharing between organizations, posing a risk to data privacy and compliance expectations.  

Steps to Reproduce

1. Create 2 JSM Projects Project A, Project B 
2. Create a Org1 In Project A 
3. Create A ticket in Project A and Org1 in the Organization Field 
4. Move the ticket from Project A to Project B 

Expected Results

When moving the ticket from Project A to Project B, The Organization Org1 should be removed 

Actual Results

 The organization from Project A (Org1) remains attached to the ticket after the move. 

Workaround

Create an automation rule to clear the organization field by utilizing  "Issue moved" trigger. 

Versions Tested

Please confirm all versions that have been tested for this issue, and indicate whether the tested version is affected or not affected, below: