-
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
Revision history does not update until page reload #17910
Labels
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/GUI
Query builder catch-all, including simple mode
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
Reporting/Dashboards
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Milestone
Comments
daltojohnso
added
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/GUI
Query builder catch-all, including simple mode
Reporting/Dashboards
.Frontend
and removed
.Needs Triage
labels
Sep 15, 2021
Reopening. See #19466 |
flamber
added
the
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
label
Dec 25, 2021
Merged
1 task
This was referenced Feb 5, 2024
Merged
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
.Frontend
Priority:P3
Cosmetic bugs, minor bugs with a clear workaround
Querying/GUI
Query builder catch-all, including simple mode
.Regression
Bugs that were previously fixed and/or bugs unintentionally shipped with new features.
Reporting/Dashboards
.Reproduced
Issues reproduced in test (usually Cypress)
Type:Bug
Product defects
Describe the bug
When you update a saved question, the change is not reflected in the History timeline because the cache of revision history entities is never cleared.
To Reproduce
Expected behavior
A new revision history entry should be immediately visible and not require a refresh after editing a question or dashboard.
Severity
p3
The text was updated successfully, but these errors were encountered: