Thanks for pointing this out, @petar777. The "All Options" Date filter widget on dashboards should be exactly the same as the graphical query builder date filter, but it isn't:

This is primarily because we haven't come up with a way to serialize times in the query string. Ideally we'd only use "url safe" characters, i.e. a-zA-Z0-9._~-. Currently we use 2018-01-01 for dates, 2018-01-01~2018-02-01 for date ranges, etc.

Maybe something like 2018-01-1_1200 (noon, for example)

This is primarily because we haven't come up with a way to serialize times in the query string. Ideally we'd only use "url safe" characters, i.e. a-zA-Z0-9._~-. Currently we use 2018-01-01 for dates, 2018-01-01~2018-02-01 for date ranges, etc.

Maybe something like 2018-01-1_1200 (noon, for example)

Genuine question, I'm probably missing some context; isn't that what percent encoding is for?

Is this feature coming still, has someone come up with a solution?
The time filter is very useful for our data and right now we're implementing a 'hack' job on the dashboard with a from hour and to hour..

A common approach I've seen is to base64 encode the parameters. Then you can use whatever transport format you like.

In JavaScript

const start = '2021-07-21T00:00:00.000Z';
const end = '2021-07-21T23:59:59Z';

const dateRangeFilter = encodeURIComponent(btoa(`${start}~${end}`));

fetch(`/query?dateRangeFilter=${dateRangeFilter}`, { method: 'POST' ... })

Produces /query?dateRangeFilter=MjAyMS0wNy0yMVQwMDowMDowMFp%2BMjAyMS0wNy0yMVQyMzo1OTo1OVo%3D

You could probably go down to millisecond level at that point with some tweaking.

This works at least in the last versions