Jira: Add option to disable issue updates #4297
Open
Conversation
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
added 4 commits
March 3, 2025 16:00
Signed-off-by: Walther Lee <[email protected]>
Signed-off-by: Walther Lee <[email protected]>
Signed-off-by: Walther Lee <[email protected]>
Signed-off-by: Walther Lee <[email protected]>
Collaborator
|
I don't know about the flag |
Member
Author
|
Sure, I can look into that. I'm pretty sure they don't overwrite, so that works too. On the other hand, without a flag, it will be a breaking change for people expecting the current implementation, which propagates changes in the receiver config to existing open issues. |
Contributor
|
Just tagging this as related/similar to #4621 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Currently, every Jira notification sends a request that overwrites user changes to issue fields (title, description, priority, etc).
Losing changes may be unexpected for many Jira users, and this PR adds a receiver config to be able to skip the update request for existing issues without affecting resolve and reopen transitions.