Repository navigation
fix(cases): enable default groups for new and linked cases - #39
Merged
johoja12 merged 2 commits intoNov 2, 2026
Merged
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
 |
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
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.
New and linked cases showed a disabled Default session group selector because only Edit Case loaded its options. Add Case now loads the owner's groups, preserves the choice across creation tabs, and saves it after creation/linking before any automatic session startup. Existing edit behavior remains; stale loads are ignored. A failed group save reports the partial success and blocks automatic startup rather than retrying case creation.
Closes #38.
Validation: 9 browser regressions and 7 existing unit tests pass. The actual desktop/mobile modal was rendered with the candidate module and production markup/styles in isolated browser contexts, with session connections and writes blocked. Selection, tab switching, reopen reset, local/remote save, stale responses and failed Docker group-save behavior were checked. Typecheck, lint, format, lockfile, frontend syntax/public assets and pre-push checks pass using private locked dependencies.
Screenshots use sample group names. This PR targets the current production keyboard candidate branch from #37 to keep its diff scoped and preserve that candidate. No production deployment is included in this change.