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

Query tables are not correctly added to a dashboard from the query page #472

Closed
madalincm opened this issue Jul 31, 2018 · 3 comments
Closed
Assignees
Milestone

Comments

@madalincm
Copy link

Steps to Reproduce:

  1. Open a query page: https://pipeline-sql.stage.mozaws.net/queries/388/source#478
  2. Click on the plus button next to the "Table" text
  3. Search for a dashboard and add the query to that dashboard
  4. Open the dashboard where you added the query: https://pipeline-sql.stage.mozaws.net/dashboard/testdashboardtoaddquery

Expected results:

The query was added to the dashboard and is correctly displayed

Actual results:

The query is added to the dashboard the the table is empty.

Notes/Issues:

Verified in FF61(Win7). Issue can be reproduced in STMO-stage
Please view this screenshot
queryaddedtodashboard

@washort
Copy link

washort commented Aug 1, 2018

Looking at the DOM, the elements for the table contents are present but for some reason not visible. Seems like a CSS issue.

@washort
Copy link

washort commented Aug 2, 2018

Looks like this is just a default-size issue. Resizing the widget displays all the data (and in your screenshot there's a scrollbar on the widget)

@washort washort closed this as completed Aug 2, 2018
@madalincm
Copy link
Author

When you add a query directly from the dashboard the behavior is different: The query table is correctly displayed.
As a user if you use the feature to add the query directly from the query page you will have to do an extra step which is to go to that dashboard and resize the the widget so data is correctly displayed.

In conclusion there are 2 different behaviors when doing the same action from 2 different places which in my opinion is a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants