| The TaskJuggler Manual | ||
|---|---|---|
| Prev | Chapter 7. Property Reference | Next |
task>
<period>
[, <period> ... ]booking
<task>
<period>
[, <period> ... ]
| |||
|---|---|---|---|
| Description | The booking attribute can be used to report completed work. This can be part of the necessary effort or the whole effort. When the scenario is scheduled in projection mode, TaskJuggler assumes that only the work reported with bookings has been done up to now. It then schedules a plan for the still missing effort. This attribute is also used within export reports to describe the details of a scheduled project. The sloppy attribute can be used when you want to skip non-working time or other allocations automatically. If it's not given, all bookings must only cover working time for the resource. | ||
| Attributes | Name | Type | Description |
task | ID | ||
period | DATEINTERVAL | ||
| Optional Attributes | overtime, sloppy | ||
| Context | resource, | ||
| Inheritable | No | Scenario Spec. | Yes |
| See also | complete, projection, sloppy, strict | ||
project prj "Project" "1.0" 2003-06-05 +1m {
# The baseline date for the projection.
now 2003-06-15
scenario plan "Plan" {
# Compute when the task will be ready based on the already done
# work and the current date.
projection { strict }
}
}
resource r1 "Resource 1"
task t1 "Task 1" {
start 2003-06-05
effort 10d
allocate r1
}
supplement resource r1 {
# This is the work that has been done up until now by r1.
booking t1 2003-06-06 +8h { sloppy 2 }
booking t1 2003-06-08 +4h,
2003-06-09 +4h { sloppy 2 }
# Book interval that extends into off-hours.
booking t1 2003-06-11-8:00 +10h { overtime 1 }
}