Constant due dates when travelling in other time zones

[Bass-T]

WHAT DO YOU RECOMMEND?

When travelling in other time zones sometimes the due date of an object changes.

These are the steps:

1. create a task

2. add a due date

3. switch the time zone to -1 (Western)

4. Check the due date (expected: same than in step 2, observed: one day before)

It’s unfortunate that the due date is automatically set to “0:00”. If the time zone is different (one hour behind), the due date jumps back a day.

See bug report:

TimeZone Switching leads to -1 day difference in date fields

Thanks for reporting this. Could you please confirm which device you are using when this happens (Android, Windows, or another platform)? Also, please share at least your Anytype app version, and if possible: • OS version • the exact steps you followed before the dates shifted Regarding your question about the workaround: currently it is not possible to change the default time for date properties (for example from 00:00 to 12:00).

AnyType is working consistent in a way which makes sense so it’s not a but - Filip asked me to raise a Feature Request to modify the behaviour of the app.

HOW COULD IT BE DONE?

When adding a due date, add 12PM instead of midnight - this would be more robust during travelling in time zones ±11 hours.

REAL WORLD USE CASES

Travelling to an earlier timezone

RECOMMENDED ALTERNATIVES

-

ADDITIONAL CONTEXT

-

[AnyFriends]

Thank you for your suggestion. It’s been added to our tracker and will be reviewed.