<< status (timesheet) << | Table Of Contents | >> statussheetreport >> |
Keyword | statussheet |
Purpose | A status sheet can be used to capture the status of various tasks outside of the regular task tree definition. It is intended for use by managers that don't directly work with the full project plan, but need to report the current status of each task or task-tree that they are responsible for. |
|
Syntax | statussheet <reporter> <interval4> [{ <attributes> }] |
|
Arguments | reporter | The ID of a defined resource. This identifies the status reporter. Unless the status entries provide a different author, the sheet author will be used as status entry author. |
interval4 | See interval4 for details. |
|
Context | properties |
Attributes | task (statussheet) |
project "test" 2009-11-30 +2m { timezone "America/Denver" trackingscenario plan now ${projectstart} } resource r1 "R1" resource r2 "R2" resource r3 "R3" task t1 "Task 1" { effort 5d allocate r1 } task t2 "Task 2" { task t3 "Task 3" { effort 10d allocate r2 } } statussheet r3 2009-12-04 { task t1 { status green "All work done" { author r1 summary "I had good fun!" details -8<- This task went smoothly and I got three things done: * Have fun * Be on time * Get things done ->8- } } task t2 { task t3 { status red "I need more time" { author r2 summary "This takes longer than expected" details -8<- To finish on time, I need help. Get this r1 guy to help me out here. * I want to have fun too! ->8- } } } }
<< status (timesheet) << | Table Of Contents | >> statussheetreport >> |