add bundling restrictions and deletion of new bundles that weren't completed on redirect #2266
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.
Reliant on maproulette/maproulette-backend#1104
There was an issue where multiple users could add the same task into their bundle, and this would cause problems on submission. The first user to submit their bundle had no issue but any other user that had bundled the same task would would get a "Bundle Failed" due to that task being officially in a bundle because of that first users submission. To prevent this issue, in this commit we made it so tasks were locked on bundle, and bundles would fail to create if they try to bundle with that now locked task, or any other locked task.
This error message will be displayed whenever a user attempts to bundle a task thats been locked since starting their session(locked tasks are filtered out on table load) to help with troubleshooting.