-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Sequence of the date of the incident overview is backwards #237
Comments
@tgrymatt you know, I've never noticed that before. Can you provide examples of where this is demonstrated please? |
Also, the issue title doesn't match the issue itself? |
Dear @jbrooksuk , yes, maybe the title of this issue is not exactly perfect. What I mean is: You have here < https://v3.cachethq.io > an option to choose a time range, which is shown in my screenshot. The order of this is 11.02.2025 - 05.02.2025 So you choose first the END of the range and the start of the range will be choosen automatically. But if you talk with someone about issues, or more concrete: About time ranges, then normally you say first the start date (wich is more in the history) and then the end date. In addition: Regarding to the order of the list... You show first the nearest date (which is logical and make sense!) it is not really a bug for me. It is just a suggestion from me. Maybe it is possible to have in the backend a settings button, which change the order of the "start - end time range chooser". |
@tgrymatt I wanted to make sure i understand the problem correctly. |
@DanielHemmati exactly! I think it should be written: Past Incidents: (Date range chooser): 01.02.2025 - 10.02.2025 No incidents reported between 2025-02-01 and 2025-02-10 And if there are some incidents reported the list should be: Incident 2025-02-10 Incident 2025-02-04 In the list: The latest incident first. |
@jbrooksuk may i work on this issue? |
In the past overviews, the date order is reversed. There it says: “No incidents reported between 2025-01-13 and 2025-01-07”, but the general way of speaking is to take the day further in the past first. It should therefore read “No incidents reported between 2025-01-17 and 2025-01-13”. The date selection fields are also reversed accordingly.
The text was updated successfully, but these errors were encountered: