#8646 carry TOA over to access popup on template change#8734
Merged
#8646 carry TOA over to access popup on template change#8734
Conversation
scolapasta
approved these changes
May 24, 2022
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
What this PR does / why we need it: Fixes an issue where the Terms of Access are not being carried over to the Restrict File popup when the user changes the template and tries to restrict a file on Dataset Create.
Which issue(s) this PR closes:
Closes #8646 Terms of Access from Template not carried over to restrict file popup
Special notes for your reviewer:
Suggestions on how to test this: In order to see the fix you must have a template with Terms of Access that are different from the default template, and restrict a file on dataset create
Does this PR introduce a user interface change? If mockups are available, please link/include them here: no
Is there a release notes update needed for this change?: no
Additional documentation: none