MallikarjunaReddyN opened a new issue, #42679:
URL: https://github.com/apache/superset/issues/42679

   ### Bug description
   
   When configuring a **Custom Timestamp Native Filter** on a dashboard, the 
filter allows users to select the same value for both the Start and End 
timestamps.
   
   The filter is accepted without any validation or warning. After applying the 
filter, the dashboard executes the query and returns an empty result set.
   
   This behavior is confusing because the UI does not indicate that the 
selected range is effectively empty.
   
   **Current Behavior**
   The filter accepts identical start and end timestamps without any validation.
   
   The dashboard executes the query and returns an empty result set without 
informing the user that the selected time range is empty.
   
   **Expected Behavior**
   One of the following should happen:
   
   - The UI should prevent applying the filter when the start and end 
timestamps are identical by displaying a validation message such as:
       `Start timestamp must be earlier than end timestamp.`
   
   OR
   
   - The UI should clearly indicate that the selected time range is empty 
before executing the query.
   
   At a minimum, users should receive feedback explaining why no results are 
returned instead of silently executing an empty-range query.
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.11
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to