Allow for specification of DNA case(s) when uploading RNA case to Scout

[karlnyr]

As a production user,
I want to be able to specify which DNA case(s) an RNA case should be uploaded to,
So that even if the DNA sample belongs to a customer that is not in a collaboration we can upload the RNA case to it as long as the subject ID's match.

Clarification:

The user scenario here is that Customer A wants to analyse RNA data from Customer B and have it uploaded to Scout. Customer A and B are not in a collaboration. Customer B approves the request and we create a case for Customer A using the sample from Customer B. We make sure that there is a DNA sample to upload the data to for Customer A, meaning that we make sure that the RNA sample has a subject ID that matches a DNA sample for Customer A. When the analysis is completed and we try to upload it will fail today, because the sample from Customer B does not have a matching DNA sample within the collaboration. To circumvent this, we should be able to specify which case(s) we want the DNA uploaded to. Then, as long as the subject ID exists in the DNA case we would do the upload that we have in place today.

Work impact

Answer the following questions:

• Is there currently a workaround for this issue? If so, what is it?
  • Yes, we can manually fetch all the reports from the RNA case and upload them manually, one by one, to the DNA case
• How much time would be saved by implementing this feature on a weekly basis?
  • This would not be a weekly occurrence, but 10 minutes per affected case
• How many users are affected by this issue?
  • All production users
• Are customers affected by this issue?
  • No

Acceptance Criteria

• A production user can specify from the CLI which case(s) an RNA case should be uploaded to.
• The upload checks for the correct DNA sample within those cases, and if there is a match allow the upload
• If there is no match, print out an informative error of which case we were unable to upload to and the reason

Notes

• Additional information.
• Dependencies.
• Related user stories.