CRDCDH-654 Export Submission on Release #250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amattu2
approved these changes
Jan 17, 2024
There was a problem hiding this comment.
Frontend implementation works as expected. The BE seems to reject the export action unless the Data Curator is marked as the "Primary Contact" for that particular data submission. Based on the two tickets:
I believe any data curator should be able to export the data submission. We can merge this after confirming the correct implementation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR aims to export a submission when it is being released.
Change Details (Specifics)
NOTE: Branch is ahead of CRDCDH-730 and should be merged afterwards
Related Ticket(s)
CRDCDH-654