Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parameters with the same name cause a conflict in dashboards #1750

Closed
caseycrogers opened this issue May 3, 2017 · 2 comments · Fixed by #2756
Closed

Parameters with the same name cause a conflict in dashboards #1750

caseycrogers opened this issue May 3, 2017 · 2 comments · Fixed by #2756

Comments

@caseycrogers
Copy link

caseycrogers commented May 3, 2017

Issue Summary

If you have a dashboard that references two or more queries that each have a non-global parameter with the same name one parameter's value will overwrite the others'.

Steps to Reproduce

  1. Create Query1 and Query2 each with a non-global template named "a_parameter".
  2. Set "a_parameter" to 1 in Query1 and 2 in Query2.
  3. Add both queries as tables to the same dashboard.
    One query's "a_parameter" value will overwrite the other query's.

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
I consider this to be a bug. I expect that, if a parameter is set to non-local, it will not interact with any other parameter in a given dashboard.

@arikfr
Copy link
Member

arikfr commented May 4, 2017

By template you mean parameter?

@caseycrogers
Copy link
Author

caseycrogers commented May 4, 2017

Yes-my bad-parameter. Updated issue.

@arikfr arikfr changed the title Templates With Same Name Conflict Parameters with the same name cause a conflict in dashboards Sep 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants