fix(config-ui): explicitly set initialValues for plugins missing it#8995
Merged
Conversation
Contributor
|
Looks good me . Approved |
bujjibabukatta
approved these changes
Jul 15, 2026
Contributor
Author
|
@klesh |
klesh
approved these changes
Jul 19, 2026
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
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.
Summary
Azure DevOps, Azure DevOps Go, Bamboo, Bitbucket Server, Jenkins, Jira,
and ZenTao configs didn't define
connection.initialValues, unlike everyother plugin. This adds it explicitly for consistency.
The actual crash from #8975 is already fixed on
mainvia #8931 — thisis just a defensive cleanup, not the fix itself.
Does this close any open issues?
Refs #8975 (already resolved by #8931)