most recent 30 from http://fogbugz.stackexchange.com 2013-05-24T11:07:42Z http://fogbugz.stackexchange.com/feeds/question/7991 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/7991/global-milestones-show-day-before-completion-date-in-case-milestone-list Kevin Berridge 2011-04-26T20:31:57Z 2012-07-31T10:30:35Z

<p>Steps to repo: 1. Create a milestone with a completion date (5/30/2011 for example) 2. Create a new case 3. Drop down the milestone select list</p> <p>RESULT: Select list displays "Milestone Name: 5/29/2011"</p> <p>EXPECTED: "Milestone Name: 5/30/2011"</p> <p>This keeps confusing our testers because the milestone date is supposed to correspond to our release date. They freak out when they see it a day early.</p>

http://fogbugz.stackexchange.com/questions/7991/global-milestones-show-day-before-completion-date-in-case-milestone-list/8146#8146 Rich Armstrong 2011-05-10T16:21:05Z 2011-05-10T16:21:05Z

<p>This might have to do with a time zone issue. Please contact us directly to resolve it.</p>

http://fogbugz.stackexchange.com/questions/7991/global-milestones-show-day-before-completion-date-in-case-milestone-list/10648#10648 Patrick Crocker 2012-07-27T16:46:01Z 2012-07-31T10:30:35Z

<p>I find that this happens if the user sets the Milestone date using a different time zone from the server.</p> <p>Example:</p> <p>FogBugz Server Time zone: Pacific Time<br> User's 'My Settings -> Options -> Time Zone': Central Time</p> <p>The user sets the Milestone date to 5/30/2011. The user is able to see the correct Milestone date, however other users in Pacific Time see 5/29/2011.</p> <p>The only work-around I found was to make sure the user sets their Time Zone option to match the server (Pacific) when they set the Milestone date. After that, the user can set their Time Zone back (Central) and everything will show correctly for all users regardless of time zone.</p> <p>Definitely a bug. Tested on versions 8.7.61.0 and 8.8.39.0.</p>