Wayne Mery (:wsmwk) Reporter
	Description • 6 years ago

Using time shortcuts for From and To, I cannot query to the most recent minutes.  It shows "to 5 hours ago."which is equivalent to my timezone offset.
 
- https://crash-stats.mozilla.com/topcrashers/?product=Thunderbird&version=59.0b1
- click first crash signature
- it gives results to very recent minutes (say 5-35 minutes)
- click show filters
- click a time shortcut, like 14 days. 
- click search

results: if time was 15:21 (which is correct local time), the search results show time of 10:21 (a differents of 5 hours) equal to my timezone. If it is really searching to 10:21 EST then no results shown for the last 5 hours.

Certain other sequences of arriving at a query and clicking a shortcut do NOT exhibit this problem.

	Wayne Mery (:wsmwk) Reporter
	Comment 1 • 6 years ago

The search URL with the incorrect results shows <2018-02-13T15%3A46%3A00.000Z

Note 15:46 is my LOCAL time, not zulu

	Wayne Mery (:wsmwk) Reporter
	Comment 2 • 6 years ago

[1] I can't reduce to less than "to 5 hours ago." even by editing the url.  it has 31 crashes for nsStringBuffer::Release
[2] Which has no signature specified, and is to the most recent minutes, shows 37 crashes for nsStringBuffer::Release


[1] https://crash-stats.mozilla.com/signature/?product=Thunderbird&version=59.0b1&signature=nsStringBuffer%3A%3ARelease&date=%3E%3D2018-02-10T11%3A47%3A52.000Z&date=%3C2018-02-13T11%3A47%3A52.000Z&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&_columns=install_time&_sort=-date&page=1#reports

[2] https://crash-stats.mozilla.com/search/?product=Thunderbird&version=59.0b1&date=%3E%3D2018-02-06T16%3A45%3A05.000Z&date=%3C2018-02-13T16%3A45%3A05.000Z&_sort=-date&_facets=signature&_facets=email&_columns=date&_columns=signature&_columns=platform&_columns=email&_columns=user_comments&_columns=uptime#facet-signature

	Wayne Mery (:wsmwk) Reporter
	Comment 3 • 6 years ago

Adrian do you know whether this is a permanent limitation?

	Will Kahn-Greene [:willkg] ET needinfo? me Assignee
	Comment 4 • 6 years ago

I think it's an issue with the ui. I don't think the API has this problem.

If it helps, I usually put the "To" a day in the future.

	Issei Horie [:is2ei]
	Comment 5 • 6 years ago

Hi Will,
I attached PR link. Could you please review it?

	Will Kahn-Greene [:willkg] ET needinfo? me Assignee
	Comment 6 • 6 years ago

Comment on attachment 8979085 [details] [review]
GitHub pull request

Removing me as reviewer. We track code review and status in GitHub and Mike is reviewing this there already.

	Issei Horie [:is2ei]
	Comment 7 • 6 years ago

I closed the PR since Flatpickr does not support UTC now.

	Osmose [:osmose, :mkelly]
	Comment 8 • 6 years ago

Re-scoping this bug to be about replacing Flatpickr, since it doesn't support UTC in a way that works with our requirements, mainly:

- All displayed dates should be in UTC.
- All dates sent to the server should be in UTC
- Clicking the shortcut links should fill the date pickers with UTC times
- The "Showing results from 3 minutes ago to now" text should be relative to the user's local time, even if the dates we're working with are UTC (otherwise, it says things like "7 hours ago" instead of "now" due to timezone offsets).

There's good browser support for date and time pickers now, so we should be using those instead.

	Issei Horie [:is2ei]
	Comment 9 • 6 years ago

Hi Michael,

Could I continue to work on this issue?

	Osmose [:osmose, :mkelly]
	Comment 10 • 6 years ago

is2ei: Thank you for the offer, but we haven't yet decided the design we want to use with the new date and time pickers, which is why I removed the "good first bug" label. I'd like to wait until we have something like that before we start work on this again.

	Issei Horie [:is2ei]
	Comment 11 • 6 years ago

(In reply to Michael Kelly [:mkelly,:Osmose] from comment #10)
> is2ei: Thank you for the offer, but we haven't yet decided the design we
> want to use with the new date and time pickers, which is why I removed the
> "good first bug" label. I'd like to wait until we have something like that
> before we start work on this again.

Osmose: I see! Thanks for your comment.

	Osmose [:osmose, :mkelly]
	Comment 12 • 6 years ago

Bumping this up to P2; I'm hearing more reports of queries behaving unexpectedly due to the time mismatch in the date filter.

	Will Kahn-Greene [:willkg] ET needinfo? me Assignee
	Comment 13 • 5 years ago

Couple of other people have been bitten by this. It's worth fixing. I'm going to grab it and see if I can get anywhere with it.