datart
datart copied to clipboard
running-elephant
Reopen: Dashboard date filter issues
Datart Version 1.0.0b4
Describe the bug With reference to https://github.com/running-elephant/datart/issues/1247, the dashboard date filters are still having inconsistencies for good user experience. The user selections are not always used as per expectation and can lead to incorrect data results.
This is regression test result, sharing for your reference and fix.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
OK: Exact date start/end filter works. The SQL uses < for end date is fine since it is not visible to user.
NOT OK: From frontend, user specified start/end timestamp should be both inclusive but SQL shows >= and <.
NOT OK: Changing from datetime to date does not reset the time to 00:00:00
NOT OK: Relative date uses 1st day of the month as reference. The end date displayed is not with SQL filter.
NOT OK: The relative date using "FROM" does not allow negative value, so effectively is same as current month. When value 2 is specified, the start date is +2 months to 1st day of current month. However, the frontend and SQL are different.
Environmental details: (optional, depending on where the bug occurs)
- OS: [e.g. Windows 10]
- Source Database: [e.g. MySQL 8.0.26]
- Browser: [e.g. chrome 94, safari 15]
Additional context Add any other context about the problem here.
We will add a new setting with user timezone setting in user profile, it will help to resolve related time issue.
We will add a new setting with user timezone setting in user profile, it will help to resolve related time issue. ok but I do not understand how timezone setting would cause this reported issue. When this new setting is available, I would check. Thank you.