export and import lockStatusSetByUser flag [MRXN23-600] #1659
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
reopening a new PR with correct branch name to link to Jira |
hotzevzl
deleted the
fix/api/MRXN23-600_export-and-import-lock-status-set-by-user-flag
branch
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.
The
lockStatusSetByUserscenario PU flag had not been added to piece exporters and importers, leading to loss of this data when cloning scenarios. This change fixes this.Testing instructions
Set some PUs to excluded, some to available and some to included for a scenario.
Clone the scenario (or its whole parent project). The new copy of the scenario must preserve the statuses set manually in the source scenario.
Feature relevant tickets
https://vizzuality.atlassian.net/browse/MRXN23-600
Checklist before submitting
develop.deploying to staging/production, please add brief testing instructions
to the deploy checklist (
docs/deployment-checklist.md)