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 580832 - Critical Path incorrect when using a non FS predecessor
Critical Path incorrect when using a non FS predecessor
Status: RESOLVED OBSOLETE
Product: planner
Classification: Other
Component: General
0.14.x
Other All
: Normal minor
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2009-04-30 04:12 UTC by Simon Fendall
Modified: 2021-06-09 20:42 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Visual Demonstration of Bug (140.09 KB, image/png)
2009-04-30 04:14 UTC, Simon Fendall 		Details

Description Simon Fendall 2009-04-30 04:12:13 UTC 
Please describe the problem:
Hey, I'm running the 0.14.3 version under Ubuntu 8.10 x86_64.
When using a system is using the unusual (read; not FS) predecessor, the critical path navigates its way correctly from the finish point up until it reaches the unusual predecessor condition. 

Steps to reproduce:
1. Create four activities.
2. Link the end of the first to the start of the second.
3. Set the predecessor of the third to require the second to have started. (SS)
4. Link the end of the third to the fourth. 
5. Enable 'Highlight Critical Tasks'


Actual results:


Expected results:


Does this happen every time?


Other information:
I'll attach a picture to the report when I figure out how.
If there's anything you would like to know, please ask. Thanks.
Comment 1 Simon Fendall 2009-04-30 04:14:12 UTC 
Created attachment 133627 [details]
Visual Demonstration of Bug
Comment 2 GNOME Infrastructure Team 2021-06-09 20:42:01 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/World/planner/-/issues/170.