Meltano Analyze - Auto Query vs. Manual "Run"
Problem to solve
(Summarize the problem we are trying to solve in the form of we need to do [A], so that [B] can [C])
We need to improve the existing UX regarding manual "Run" hits and automatic query generation so that users can efficiently and reliably run queries of varying elapsed times with UI feedback expectations regarding run length/complexity.
Target audience
(For whom are we doing this? Include a persona)
Analyze users
Further details
(Include use cases, benefits, and/or goals)
Clear feedback in the UI and potentially interactive options (maybe as simple as a checkbox to autorun queries or not) so users have clear expectations regarding long-running queries which subsequently manifests as visualization and table updates at runtime.
Proposal
(How are we going to solve the problem? Try to include the user journey)
We need to think deeply through the scenarios, but the simplest solution would be to add a checkbox for "autorun" that the user can toggle unless we decide the default of auto is OK (this is currently how it works after the initial "Run" hit).
What does success look like, and how can we measure that?
(Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this)
Success is having the UI properly provide feedback and/or interactive options so the user's UX aligns with expectations.
Regression test
(Ensure the feature doesn't cause any regressions)
-
Write adequate test cases and submit test results -
Test results should be reviewed by a person from the team
Links / references
Please note that this was taken from GitLab, to be changed accordingly
Tasks
-
likely dropdown with checkbox solution - [-] likely add UI element over graph/table communicating the reloading