Bug:

[karlnyr]

Describe the bug

When Customer A requests to analyze RNA data from Customer B and have it uploaded to Scout, the process fails because the sample from Customer B does not have a matching DNA sample within Customer A’s collaboration. Despite ensuring the RNA sample has a subject ID matching a DNA sample for Customer A, the upload fails because the DNA case does not exist in the collaboration context.

To Reproduce

1. Customer A requests RNA data analysis from Customer B.
2. Customer B approves the request.
3. A case for Customer A is created using the RNA sample from Customer B.
4. Ensure the RNA sample’s subject ID matches a DNA sample for Customer A.
5. Complete the RNA analysis.
6. Attempt to upload the data to Scout.

Expected behavior

The case must not be uploaded to the customer (Customer B) owning the RNA data unless Customer A and Customer B are in a collaboration.

If Customer A and Customer B are not in a collaboration, the system should:

1. Check for matching DNA cases within Customer A’s data.
2. Proceed with the upload only if such DNA cases exist.
3. Fail the upload if no matching DNA cases are found in Customer A’s data, as per standard workflow.Additional context

Add any other context about the problem here.

• This issue arises due to limitations in handling cross-customer data ownership in non-collaborative contexts.
• An enhancement is needed to verify and enforce the use of DNA cases belonging to the customer who ordered the analysis (Customer A) when uploading the RNA data. Something like Allow for specification of DNA case(s) when uploading RNA case to Scout #4074
• Currently we are updating analysis for customers who did not request it. In production we cannot remove these analyses either without removing the case from Scout. It is VERY important that we disable this kind of behaviour.