For clarity (and to forestall anyone asking): "...we should have the user enter the day and time. That would be converted internally to epoch time based on the entering user's timezone. Then it would be displayed to users based on their own timezones."
+1 to adding a time field to Milestone duedate. -M On Sep 20, 4:39 pm, Eli Carter <[EMAIL PROTECTED]> wrote: > All, > > I'm coming to the conclusion that r6012 isn't sufficient to solve #6028. > > Having a due /date/ for a milestone is ambiguous once you have users in > different timezones. The due date is taken to be midnight in the setting > user's timezone of that day. When another user only one timezone away looks > at that same due date, they may see a different date. > > If we specify that the date given is taken to be midnight UTC on that date, > the date the user sees may not match the date entered. > > I think we really need to make the due date be a date and time. That avoids > the ambiguity. (It has a plus for businesses that want to specify midnight > or 'end-of-business' of a day as when it is due.) > > Comments, thoughts, etc? > > Eli --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
