Bug 135505 - strict booking problem on beta2
Summary: strict booking problem on beta2
Status: RESOLVED WONTFIX
Alias: None
Product: TaskJuggler
Classification: SUSE Tools
Component: Commandline Tool (show other bugs)
Version: TaskJuggler
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Klaas Freitag
QA Contact: Klaas Freitag
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-24 22:19 UTC by zebulon zebulon
Modified: 2009-07-14 20:07 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
project with problem (1.92 KB, application/octet-stream)
2005-11-24 22:23 UTC, zebulon zebulon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description zebulon zebulon 2005-11-24 22:19:22 UTC
the project cannot be scheduled when a task have it's booking started and is scheduled with a now date inside the current working hour. if I virtually move the now date just before 9:0 in our case it works.

link: the project with problem
http://www.taskjuggler.org/FUDforum2/index.php?t=tree&th=2722&mid=6215&S=4bf786d2f54d368174b96376fe0673e9&rev=&reveal=

another minor problem: it seems that choosing a scenario for htmlstatusreport does not works.
Comment 1 zebulon zebulon 2005-11-24 22:23:03 UTC
Created attachment 58648 [details]
project with problem
Comment 2 Chris Schlaeger 2005-11-30 17:05:39 UTC
I'm planning for round all dates to the timing resolution. This will eliminate this problem. But this is too much of an intrusive change to make right before the 2.2 release. So I'll leave it in for now.

On the scenario issue: this should work for the individual tables. It will not work for the statusreport globally. This is because you need to provide the filter functions for hidetask again, as they also include the scenario.
Comment 5 Stefan Behlert 2009-07-14 20:07:03 UTC
Closing after three years of inactivity.