docs(changelog): note groups findGroups legacy group_id fix under 25.03.X#7582
Merged
Merged
Conversation
…03.X Pairs with the actual fix in countly-enterprise-plugins PR #3179 (mirror of countly-platform #295). Read-path coercion in plugins/groups/api/services/dbService.js so pre-2021 members docs with group_id stored as a string no longer trip MongoDB Location40081 on the new $in-based $lookup pipeline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Cookiezaurs
approved these changes
May 21, 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
2 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
Adds a 25.03.X changelog entry for the groups
findGroupslegacygroup_idregression fix. The actual code change lives in the plugins repo (see "Related" below) — this PR only updatesCHANGELOG.mdso the next 25.03.X release notes reflect the fix.Why
Two customers hit
MongoServerError: ... $in requires an array as a second argument, found: string(MongoLocation40081) after upgrading to v25.03.43, breaking the groups listing, User Management, Alerts and Preset Management screens. The new$lookuppipeline introduced in countly-platform6fe036e3addoes$in: ["$$group_id", { $ifNull: ["$group_id", []] }]againstmembers.group_id, which throws when the field is a string (pre-2021 schema, befored66a83b096).Related
Tests
No code changes here —
CHANGELOG.mdonly. The fix itself is covered by a newLegacy string group_id toleranceintegration test in the plugins PR.