Clarify options for 'offset' on date field filters

May not need usability review actually.

Change is better but not clear now you can do -2 -30 minutes combined now. Will see what the committer thinks.

For me we should close this as "won't fix works as designed". I think the help is useful it is showing you that -2 hours -30 minutes is how to subtract 2 and a half hours using this field. Because -2 hours 30 minutes will only subtract one and a half hours.

+1 for that

Hmm, I think our example here is a little obscure in syntax, even though it might be correct. But as it isn't an uncommon scenario to try and offset by parts of hours, and it has a weird-ish syntax, it does provide value. We might do a better job of explaining what the expected outcome of the value is maybe? If we want to do anything at all?

Should we close this and tag 🐛 Date/time Views filter tries strotime() relative to Unix epoch Needs work as needing to update these examples? If that lands we might be able to link to strtotime I think?

If we think this won't make it I think moving that over makes sense.

Since the docs aren't wrong, moving this to a task.

Options I see:

1. Remove the "-2 hours -30 minutes" example since its vague syntax (feels bad since it is a correct example)
2. Add additional explanation to the "-2 hours -30 minutes" example at to the expected outcome, maybe explain that "-2 hours 30 minutes" does something else (feel over the top)
3. Update 🐛 Date/time Views filter tries strotime() relative to Unix epoch Needs work to also update the examples provided, or link to strtotime docs (which currently doesn't provide an example like "-2 hours -30 minutes")

I'm going to implement 3, if somebody feel strongly that we should do another option, feel free to reopen this.