# Disabling report descriptions causes other descriptions to be hidden
**URL:** https://meta.discourse.org/t/topic/405254
**Category:** Bug
**Tags:** fixed, bug
**Created:** [June 13, 2026, 12:09pm UTC](https://meta.discourse.org/t/topic/405254 "2026-06-13T12:09:17Z")
**Posts on this page:** 1
**Showing post:** 2
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [June 15, 2026, 3:17pm UTC](https://meta.discourse.org/t/topic/405254/2 "2026-06-15T15:17:50Z")
Sorry about that, issue should be fixed by
>
>
> Previously, flag names with no ASCII word characters (e.g. Chinese) all normaliz…ed to the same \`name\_key\` of \`custom\_\`, because \`set\_name\_key\` stripped non-\`\\w\` characters and Ruby's \`\\w\` is ASCII-only. The flag system keys lookups by \`name\_key\` (the \`disabled\_flag\_types\` enum, the frontend \`actionByName\` map), so once two flags shared a key, disabling one of them flipped \`can\_act\` for the whole group and hid every other flag that shared it.
>
> This makes \`name\_key\` reliably unique:
>
> \- \`set\_name\_key\` falls back to \`custom\_flag\` when the slug is empty and appends a counter (\`\_2\`, \`\_3\`, ...) on collision, so distinct names always produce distinct keys. It now only re-derives the key when the name actually changes, keeping it stable across other saves.
> \- A post-deploy migration backfills existing duplicate keys and adds the unique index on \`flags.name\_key\` that the original \`create\_flags\` migration intended (\`unique: true\` is a no-op in \`create\_table\`).
>
> https://meta.discourse.org/t/405254
---
_[View the full topic](https://meta.discourse.org/t/topic/405254)._