[ templating ] [ `custom` type ] `key : value` pairs break with duplicate `value`

[PaddyProdapt]

What happened:
Key with same values are disabled in the drop down menu for custom template variable (key/Value)

What you expected to happen: Key with same values should not be disabled in the drop down menu PFA snaps

How to reproduce it (as minimally and precisely as possible): Try to create custom variable (key : value) with different key names but same value

Anything else we need to know?:

Environment:

• Grafana version: 8.2.1 and 7.5.8
• Data source type & version: NA
• OS Grafana is installed on: Linux
• User OS & Browser: Chrome and firefox
• Grafana plugins: NA
• Others: NA

[zuchka]

Hi @PaddyProdapt, thanks for making this issue. Digging into this, I too am noticing some buggy behavior with the custom variables. Our docs say to enter key-value pairs as key : value but previewing the variables suggests the opposite: value : key.

I made a dashboard with four variables, iterating through combinations of k1 : v1,k2 : v2 where k1 == k2 or v1 == v2 etc etc (this assumes the documentation pattern of key : value, ...):

each one behaves a little differently. maybe this is buggy behavior or maybe we need docs improvement 🤷 ?

https://play.grafana.org/d/xU2hgWdnk/mja-002?orgId=1

[ashharrison90]

hey @PaddyProdapt 👋

can you explain a bit more about your use case for having different variables with the same value? why do you need this?

thanks! 😄

[PaddyProdapt]

Hi @ashharrison90 , There is many use case for this.
One example :
Consider "Location : host" as a custom variable which have 10 location (key) In which three have same host name. In that case I will not be able to select those three if any one is selected.

PS : Users will not only use values in dashboards, sometimes they will also use key name directly.

[ashharrison90]

we've delivered a visual fix that should go out in the upcoming 8.2.2 release.

disclaimer: this almost certainly won't fix every problem with variables that have the same value. it's not really a use case that was considered when developing variables. but it should at least display the correct label in the dropdown when selecting.