Eventually the PC where i run fossil has troubles with your internal date. So, i.e, new tickets are saved with date 01-01-2000 and become listed in first places. Unlucky it isn't ever evident for the user and least for the rest of the team.

I think that fossil may show a warning for ask if the date is right because isn't later as expected.

I don't know if this problem is common in other scenarios, but i believe that is most usual than anybody think in microdevelopments.

Wherever, i guess will require minor fixes for keep ever safe the date's sequence in any situation possible.