-
Notifications
You must be signed in to change notification settings - Fork 12k
-
Notifications
You must be signed in to change notification settings - Fork 12k
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
grafana 2.2.0-pre Dashboard Link variable values into Repeat Panel #2564
Comments
using influx 0.9.2 if that matters |
I think this was fixed 4 days ago, 0d8303c Can you try a more recent build if 2.2 |
tried the latest from this morning, same thing. some more details:
|
ok, the fix in 0d8303c contained a subtle bug :( Fixed now, will push out new 2.2 builds now |
works gr8 - nice job @torkelo and awesome product! |
torkelo
added a commit
that referenced
this issue
Aug 22, 2015
…plate var used in repeat panel from url), fixes #2564 Conflicts: CHANGELOG.md
donh
pushed a commit
to donh/grafana
that referenced
this issue
Nov 12, 2015
…lue template var used in repeat panel from url), fixes grafana#2564
donh
pushed a commit
to donh/grafana
that referenced
this issue
Nov 12, 2015
…lue template var used in repeat panel from url), fixes grafana#2564 Conflicts: CHANGELOG.md
donh
pushed a commit
to donh/grafana
that referenced
this issue
Nov 12, 2015
…lue template var used in repeat panel from url), fixes grafana#2564
donh
pushed a commit
to donh/grafana
that referenced
this issue
Nov 12, 2015
…lue template var used in repeat panel from url), fixes grafana#2564 Conflicts: CHANGELOG.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When having a dashboard with - Settings - Links type dashboard enabled and "add current variable values" spawning into a dashboard which uses Repeat Panel on for example "host" it doesnt repeat the panels from the $host selection from "parent" dashboard. (this worked in 2.1)
The text was updated successfully, but these errors were encountered: