GNOME Bugzilla – Bug 156615
Project Start Date Keeps Moving Around
Last modified: 2005-02-21 08:36:43 UTC
I started up a project, put some stuff in and realized it was starting from today. Went in to Project Properties and changed it to the correct date (11/17). Hit OK, look at Gant Chart and it has the day before (11/16). Then, I re-open Project Properties and it now has the start date as the day before that (11/15). If I save that, it now stays at that date (11/15). Tried with both 0.12.1 and current CVS.
Hm I can't reproduce this. Which locale and timezone are you in? Could you try running planner with: LANG=C planner and see if it does the same?
I'm a new *user* (this was installed for me by company sysadmin) - Planner provides much-needed management functionality. However, this bug is a show-stopper. I'm using a fresh install of Planner 0.12 on Debian Testing - "sarge" I believe. I'm on MST in Moab Utah. I encountered this bug yesterday as soon as I tried to create my first new project. Because the documentation emphasizes the importance of the Start Date, I have not yet spent time creating tasks or editing the Gantt chart yet. 1. Create New project. 2. Project > Edit Project Properties. 3. Enter Name <tab> 4. Accept default Start date of 11/21/04 <tab> 5. The date changes to 11/20/04 as soon as the cursor hits the Manager field. The date changes concurrently in the Resource Usage, Gantt, and Task windows. (Note that I get the same behavior if I enter a Start date in either the past or the future.) 6. Enter Manager <tab> 7. Enter Organization. Click Close. [INTERFACE NOTE: OK and Cancel buttons would be nice.] 1. Reopen the Project Properties windows. The Start date displayed on opening is incremented down a day on open. 2. Click Close. The Project start date displayed in Resource Usage, Gantt, and Task views increments down a day also to match. 3. Repeat open and close. Date increments down 1 day each time. Please upgrade Priority and Severity to Immediate/Blocker. Very good product is unusable until this is addressed. Thank you!
I can't reproduce this so I need someone who can to debug it. Setting different priority or severity doesn't really affect how fast this will be fixed. Which locale are you using? You can see this by typing "locale" in a terminal.
Locale is POSIX, apparently. (My sysadmin says stable distribution boxes are all C but testing is POSIX.) ecsedym@ninlil:~$ locale LANG=POSIX LC_CTYPE="POSIX" LC_NUMERIC="POSIX" LC_TIME="POSIX" LC_COLLATE="POSIX" LC_MONETARY="POSIX" LC_MESSAGES="POSIX" LC_PAPER="POSIX" LC_NAME="POSIX" LC_ADDRESS="POSIX" LC_TELEPHONE="POSIX" LC_MEASUREMENT="POSIX" LC_IDENTIFICATION="POSIX" LC_ALL= Thank you for clarification on priority/severity designations.
I'm seeing this too. I'm running a pretty much stock install of Debian Testing. jeremy@workjava:~$ locale LANG=en_US LC_CTYPE="en_US" LC_NUMERIC="en_US" LC_TIME="en_US" LC_COLLATE="en_US" LC_MONETARY="en_US" LC_MESSAGES="en_US" LC_PAPER="en_US" LC_NAME="en_US" LC_ADDRESS="en_US" LC_TELEPHONE="en_US" LC_MEASUREMENT="en_US" LC_IDENTIFICATION="en_US" LC_ALL=
*** Bug 161259 has been marked as a duplicate of this bug. ***
*** Bug 158108 has been marked as a duplicate of this bug. ***
It would be great if people could try current CVS since it has a calendar widget added to select the date with. Also please try the entry and see if it still misbehaves. Try different dates and date formats, that would help me find what's wrong.
By the way, which timezone are you guys in? cat /etc/timezone
America/New_York I compiled yesterday, will see if I can still reproduce.
Still happening with CVS as of 2005/02/19 13:21 America/New_York
Both when setting the date with the calendar and when entering in manually?
Could you try the attached patch and paste the output here from just opening and closing the project properties dialog?
I've committed a change that might fix this, please let me know if it does.
Ooops, I attached to the wrong bug, this is what I was referring to: http://bugzilla.gnome.org/attachment.cgi?id=37719&action=view But try the latest CVS first, it might be fixed there.
CVS seems to have fixed it.