-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
X-ray card links & drill-throughs are broken #19405
Labels
Priority:P2
Average run of the mill bug
Querying/X-rays
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Comments
Regression on master. Works on 0.41.5. |
Yep, caused by #19027. X-ray dashcards are a special case that needs to be handled differently. |
nemanjaglumac
added a commit
that referenced
this issue
Mar 31, 2022
This was referenced Nov 21, 2022
This was referenced Dec 23, 2022
Merged
This was referenced Jan 3, 2023
This was referenced Apr 30, 2024
Merged
Closed
This was referenced May 7, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Priority:P2
Average run of the mill bug
Querying/X-rays
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Describe the bug
If you're viewing an (unsaved) X-ray, and you click on the title of any card, it takes you to the "Ask a question" page with the simple question/custom question/native query prompts, rather than taking you to the specific question that you clicked on.
And if you try to do a drill-through or breakout on any card on the X-ray, it'll take you to a 404 page.
Untitled.mov
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Links should take you directly to the question you clicked on
Information about your Metabase Installation:
Current master (& can repro on stats)
The text was updated successfully, but these errors were encountered: