Context:

Dashboard filters have a flag called "allowCustomValues" which, when true, allows viewers of Dashboards to add filter values for existing dashboard filters. However, the naming of this is confusing because some filters now allow "custom values", ie you can filter for a value that has not yet occurred in the data.

To avoid confusion, lets rename the flag to something that's a bit more clear.

AT:

• The allowCustomValues flag is renamed to differentiate it from custom values in filters
• Existing data is migrated
• The FE is adjusted accordingly
• Confluence documentation is adjusted accordingly