Werk #22090: Fix unpredictable winner among views published by several users
| Component | User interface | ||||
| Title | Fix unpredictable winner among views published by several users | ||||
| Date | Aug 3, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
What changed
If two or more users published a customized view under the same name, it was undefined which of them the other users actually got to see. The winner depended on the order in which the site happened to read the user profile directories from disk, so it could silently change again after any user saved any view.
The same applied to dashboards and reports.
From now on the visual owned by the alphabetically first user ID wins. That decision is stable for all users, across page reloads and across restarts.
Why this matters
Two administrators customizing and publishing the same built-in view is not exotic, and until now the result was a coin flip that could flip again later. If you ran into a view that "changed by itself", this was very likely the reason.
Technical background
The precedence between your own visuals, visuals published by users holding the "Modify built-in views" permission, built-in visuals, published visuals of other users and packaged visuals is unchanged. Only the tie between several equally privileged publishers of the same name is now broken deterministically instead of by directory iteration order.
If such a name collision exists on your site, the visual you see may change with this update - this time to the one that will keep showing up. To get rid of the ambiguity for good, rename one of the two visuals.