NO-SNOW change jira assignee, labels, priority #2119
Merged
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
sfc-gh-dszmolka
added
NO-CHANGELOG-UPDATES
sfc-gh-dszmolka
requested review from
sfc-gh-mkeller,
sfc-gh-aling,
sfc-gh-dyadav and
a team
sfc-gh-dprzybysz
approved these changes
Dec 13, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
No driver code was changed, issue is only affecting Jira creation workflow.
Jiras today are created and assigned incorrectly. Autogenerated jiras should now have a different base assignee and priority to match internal flows. Also adding the label to reflect issue origin (oss).