Fix: watchers not saved when creating issues/tasks/user stories via API ([Bug] #138)#227
Open
YaruG1022 wants to merge 5 commits into
Open
Conversation
YaruG1022
changed the title
YaruG1022
changed the title
YaruG1022
changed the title
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
1 participant
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.
Watchers specified at creation time via the API were silently discarded due to an early return in restore_object() when instance=None. Fixed by deferring watcher assignment to save() after the object is persisted, and changed _old_watchers default from None to [] to prevent a secondary TypeError in post-save notifications. Unit and integration regression tests were added for issues, tasks, and user stories.
This change request addresses [Bug] #138.