After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 151601 - Predecessor lag is in hour increments, not days, as indicated in 0.12.0 and 0.12.1
Predecessor lag is in hour increments, not days, as indicated in 0.12.0 and 0...
Status: RESOLVED DUPLICATE of bug 132357
Product: planner
Classification: Other
Component: General
0.12
Other Linux
: Normal normal
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2004-09-01 13:12 UTC by Tim Cradic
Modified: 2005-02-18 17:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim Cradic 2004-09-01 13:12:05 UTC 
When setting a lag for a task the delay that is indicated correlates to hours
whether it is referenced from FS or SS.  It takes an entry of 25 to show a lag
of 2 days (one day + one hour).  This also shows over weekends.  If the
predecessor ends on Friday a lag of 1 hour shows the task starting on Monday. 
But to get the task to start on Tuesday the lag must be for 73. (3days+1hour). 
Tried typing 73d and got the same result.
Comment 1 Richard Hult 2005-02-18 17:56:35 UTC 
*** This bug has been marked as a duplicate of 132357 ***