taskjuggler 0.2.1 → 0.2.2

data/test/TestSuite/StatusSheetTemplates/project.tji

@@ -1,35 +0,0 @@
-# --------8<--------8<--------
-statussheet a 2010-05-03-00:00-+0200 - 2010-05-10-00:00-+0200 {
-
-  # Task: Project
-  task p.t1.t2 {
-    # status green "JE1" {
-    #   # Date: 2010-05-04-00:00-+0200
-    #   author c
-    # }
-  }
-
-  task p.t1.t3 {
-    # status green "JE2" {
-    #   # Date: 2010-05-06-00:00-+0200
-    #   author c
-    # }
-  }
-
-  task p.t1.t6 {
-    # status green "JE4" {
-    #   # Date: 2010-05-06-00:00-+0200
-    #   author f
-    # }
-  }
-
-  task p.t4.t5 {
-    # status green "JE3" {
-    #   # Date: 2010-05-06-00:00-+0200
-    #   author e
-    # }
-  }
-
-}
-# -------->8-------->8--------
-

data/test/TestSuite/StatusSheetTemplates/project.tjp

@@ -1,56 +0,0 @@
-project "Test" 2010-04-28 +3m
-
-resource a "A"
-resource b "B"
-resource c "C"
-resource d "D"
-resource e "E"
-resource f "F"
-
-task p "Project" {
-  responsible a
-  task t1 "T1" {
-    responsible b
-    task t2 "T2" {
-      effort 10d
-      allocate c
-      journalentry 2010-05-04 "JE1" {
-        author c
-        alert green
-      }
-    }
-    task t6 "T6" {
-      effort 10d
-      allocate f
-      journalentry 2010-05-06 "JE4" {
-        author f
-        alert green
-      }
-    }
-    task t3 "T3" {
-      effort 10d
-      allocate c
-      journalentry 2010-05-06 "JE2" {
-        author c
-        alert green
-      }
-    }
-  }
-  task t4 "T4" {
-    responsible d
-    task t5 "T5" {
-      effort 5d
-      allocate e
-      journalentry 2010-05-06 "JE3" {
-        author e
-        alert green
-      }
-    }
-  }
-}
-
-statussheetreport "project" {
-  period 2010-05-03 +1w
-  hideresource ~(plan.id = "a")
-  sorttasks id.up
-}

data/test/TestSuite/StatusSheets/TimeSheets/2002-03-01/missing-reports

@@ -1,2 +0,0 @@
-resource1
-resource2

data/test/TestSuite/StatusSheets/boss.tji

@@ -1,45 +0,0 @@
-# --------8<--------8<--------
-statussheet boss 2002-03-02-00:00-+0100 {
-
-  # Task: Accounting Software
-  task AcSo.software.database {
-    status red "Problems with the SQL Libary" {
-      # Date: 2002-02-03-00:00-+0100
-      author dev1
-      summary -8<-
-      We ran into some compatibility problems with the SQL
-      Library.
-      ->8-
-      details -8<-
-      We have already contacted the vendor and are now waiting for
-      their advise.
-      ->8-
-    }
-  }
-
-  task AcSo.manual {
-    status green "User manual completed" {
-      # Date: 2002-02-28-00:00-+0100
-      author boss
-      summary -8<-
-      The doc writers did a really great job to finish on time.
-      ->8-
-    }
-  }
-
-  task AcSo.test.alpha {
-    status yellow "Contract with Peter not yet signed" {
-      # Date: 2002-03-01-00:00-+0100
-      author boss
-      summary -8<-
-      The paperwork is stuck with HR and I can't hunt it down.
-      ->8-
-      details -8<-
-      If we don't get the contract closed within the next week,
-      the start of the testing is at risk.
-      ->8-
-    }
-  }
-
-}
-# -------->8-------->8--------

data/test/TestSuite/StatusSheets/boss_mail

@@ -1,51 +0,0 @@
-Date: Wed, 03 Mar 2010 09:46:45 +0100
-From: phb@crappysoftware.com
-To: statussheets@taskjuggler.foo.bar
-Message-ID: <4b8e21f53542c_17764375603597b@mime.mail>
-Subject: Your weekly report template for 2002-03-01
-
-# --------8<--------8<--------
-statussheet boss 2002-02-23-00:00-+0000 - 2002-03-02-00:00-+0000 {
-
-  # Task: Accounting Software
-  task AcSo.software.database {
-    status red "Problems with the SQL Libary" {
-      # Date: 2002-02-03-00:00-+0100
-      author dev1
-      summary -8<-
-      We ran into some compatibility problems with the SQL
-      Library.
-      ->8-
-      details -8<-
-      We have already contacted the vendor and are now waiting for
-      their advise.
-      ->8-
-    }
-  }
-
-  task AcSo.manual {
-    status green "User manual completed" {
-      # Date: 2002-02-28-00:00-+0100
-      author boss
-      summary -8<-
-      The doc writers did a really great job to finish on time.
-      ->8-
-    }
-  }
-
-  task AcSo.test.alpha {
-    status yellow "Contract with Peter not yet signed" {
-      # Date: 2002-03-01-00:00-+0100
-      author boss
-      summary -8<-
-      The paperwork is stuck with HR and I can't hunt it down.
-      ->8-
-      details -8<-
-      If we don't get the contract closed within the next week,
-      the start of the testing is at risk.
-      ->8-
-    }
-  }
-
-}
-# -------->8-------->8--------

data/test/TestSuite/StatusSheets/dev2_mail

@@ -1,37 +0,0 @@
-Date: Wed, 03 Mar 2010 09:50:41 +0100
-From: foo@bar.com
-To: SBono@crappysoftware.com
-Message-ID: <4b8e22e125168_180b43756010458@mime.mail>
-Subject: Your weekly report template for 2002-03-01
-
-Hello Sebastien Bono!
-
-Please find enclosed your weekly status report template. Please fill out the
-form and send it back to the sender of this email. You can either use the
-attached file or the body of the email. In case you send it in the body of the
-email, make sure it only contains the 'statussheet' syntax. It must be plain
-text, UTF-8 encoded and the status sheet header from 'statussheet' to the period
-end date must be in a single line that starts at the beginning of the line.
-
-# --------8<--------8<--------
-statussheet dev2 2002-02-23-00:00-+0000 - 2002-03-02-00:00-+0000 {
-
-  # Task: Software Development
-  task AcSo.software.database {
-    status green "A Bug" {
-      # Date: 2002-02-03-00:00-+0100
-      author dev1
-      summary -8<-
-      We ran into some compatibility problems with the SQL
-      Library.
-      ->8-
-      details -8<-
-      We have already contacted the vendor and are now waiting for
-      their advise.
-      For details see http://bugzilla.com/bugs/show_bug.cgi?id\=647
-      ->8-
-    }
-  }
-
-}
-# -------->8-------->8--------

data/test/TestSuite/StatusSheets/project.tjp

@@ -1,275 +0,0 @@
-project "Accounting Software"  2002-01-16 +4m {
-  # Hide the clock time. Only show the date.
-  timeformat "%Y-%m-%d"
-  # Use US format for numbers
-  numberformat "-" "" "," "." 1
-  # Use US financial format for currency values. Don't show cents.
-  currencyformat "(" ")" "," "." 0
-  # Pick a day during the project that will be reported as 'today' in
-  # the project reports. If not specified, the current day will be
-  # used, but this will likely be outside of the project range, so it
-  # can't be seen in the reports.
-  now 2002-03-05-13:00
-  # The currency for all money values is the Euro.
-  currency "USD"
-
-  # We want to compare the baseline scenario to one with a slightly
-  # delayed start.
-  scenario plan "Plan" {
-    scenario delayed "Delayed"
-  }
-  extend resource {
-    text Phone "Phone"
-  }
-}
-
-# This is not a real copyright for this file. It's just used as an example.
-copyright "© 2002 Crappy Software, Inc."
-
-# The daily default rate of all resources. This can be overridden for each
-# resource. We specify this, so that we can do a good calculation of
-# the costs of the project.
-rate 390.0
-
-# Register Good Friday as a global holiday for all resources.
-vacation "Good Friday" 2002-03-29
-flags team, manager
-
-# This is one way to form teams
-macro allocate_developers [
-  allocate dev1
-  allocate dev2
-  allocate dev3
-]
-
-# In order to do a simple profit and loss analysis of the project we
-# specify accounts. One for the development costs, one for the
-# documentation costs, and one account to credit the customer payments
-# to.
-account cost "Project Cost" {
-  account dev "Development"
-  account doc "Documentation"
-}
-account rev "Payments"
-# The Profit&Loss analysis should be rev - cost accounts.
-balance cost rev
-
-resource boss "Paul Henry Bullock" {
-  email "phb@crappysoftware.com"
-  Phone "x100"
-  rate 480
-  flags manager
-}
-resource dev "Developers" {
-  resource dev1 "Paul Smith" {
-    email "paul@crappysoftware.com"
-    Phone "x362"
-    rate 350.0
-  }
-  resource dev2 "Sébastien Bono" {
-    email "SBono@crappysoftware.com"
-    Phone "x234"
-    flags manager
-  }
-  resource dev3 "Klaus Müller" {
-    email "Klaus.Mueller@crappysoftware.com"
-    Phone "x490"
-    vacation 2002-02-01 - 2002-02-05
-  }
-
-  flags team
-}
-resource misc "The Others" {
-  resource test "Peter Murphy" {
-    email "murphy@crappysoftware.com"
-    Phone "x666"
-    limits { dailymax 6.4h }
-    rate 310.0
-  }
-  resource doc "Dim Sung" { 
-    email "sung@crappysoftware.com"
-    Phone "x482"
-    rate 300.0 
-    vacation 2002-03-11 - 2002-03-16
-  }
-
-  flags team
-}
-
-# Now we specify the work packages. The whole project is described as
-# a task that contains subtasks. These subtasks are then broken down
-# into smaller tasks and so on. The innermost tasks describe the real
-# work and have resources allocated to them. Many attributes of tasks
-# are inherited from the enclosing task. This saves you a lot of typing.
-task AcSo "Accounting Software" {
-
-  # All work-related costs will be booked to this account unless the
-  # subtasks specify something different.
-  chargeset dev
-  # For the duration of the project we have running cost that are not
-  # included in the labor cost.
-  charge 170 perday
-  responsible boss
-
-  task spec "Specification" {
-    # The effort to finish this task is 20 man-days.
-    effort 20d
-    # Now we use the macro declared above to allocate the resources
-    # for this task. Because they can work in parallel, they may finish this
-    # task earlier than in 20 working-days.
-    ${allocate_developers}
-    # Each task without subtasks must have a start or an end
-    # criterion and a duration. For this task we use a reference to a
-    # milestone defined further below as the start criterion. So this task
-    # can not start before the specified milestone has been reached.
-    # References to other tasks may be relative. Each exclamation mark (!)
-    # means 'in the scope of the enclosing task'. To descent into a task, the
-    # fullstop (.) together with the id of the tasks have to be specified.
-    depends !deliveries.start
-  }
-
-  task software "Software Development" {
-
-    # The software is the most critical task of the project. So we set
-    # the priority of this task (and all its subtasks) to 1000, the top
-    # priority. The higher the priority, the more likely the task will
-    # get the requested resources.
-    priority 1000
-
-    # All subtasks depend on the specification task.
-    depends !spec
-    responsible dev2
-
-    task database "Database coupling" {
-      effort 20d
-      allocate dev1, dev2
-      journalentry 2002-02-03 "Problems with the SQL Libary" {
-        author dev1
-        alert yellow
-        summary -8<-
-          We ran into some compatibility problems with the SQL
-          Library.
-        ->8-
-        details -8<-
-          We have already contacted the vendor and are now waiting for
-          their advise.
-        ->8-  
-      }
-    }
-
-    task gui "Graphical User Interface" {
-      effort 35d
-      # This task has taken 5 man-days more than originally planned.
-      # We record this as well, so that we can generate reports that
-      # compare the delayed schedule of the project to the original plan.
-      delayed:effort 40d
-      depends !database, !backend
-      allocate dev2, dev3
-    }
-
-    task backend "Back-End Functions" {
-      effort 30d
-      # This task is behind schedule, because it should have been
-      # finished already. To document this, we specify that the task
-      # is 95% completed. If nothing is specified, TaskJuggler assumes
-      # that the task is on schedule and computes the completion rate
-      # according to the current day and the plan data.
-      complete 95
-      depends !database
-      allocate dev1, dev2
-    }
-  }
-
-  task test "Software testing" {
-
-    task alpha "Alpha Test" {
-      # Efforts can not only be specified as man-days, but also as
-      # man-weeks, man-hours, etc. By default, TaskJuggler assumes
-      # that a man-week is 5 man-days or 40 man-hours. These values
-      # can be changed, of course.
-      effort 1w
-      # This task depends on a task in the scope of the enclosing
-      # task's enclosing task. So we need two exclamation marks (!!)
-      # to get there.
-      depends !!software
-      allocate test, dev2
-      note "Hopefully most bugs will be found and fixed here."
-      journalentry 2002-03-01 "Contract with Peter not yet signed" {
-        author boss
-        alert red
-        summary -8<-
-          The paperwork is stuck with HR and I can't hunt it down.
-        ->8-
-        details -8<-
-          If we don't get the contract closed within the next week,
-          the start of the testing is at risk.
-        ->8-
-      }
-    }
-
-    task beta "Beta Test" {
-      effort 4w
-      depends !alpha
-      allocate test, dev1
-    }
-  }
-
-  task manual "Manual" {
-    effort 10w
-    depends !deliveries.start
-    allocate doc, dev3
-    purge chargeset
-    chargeset doc
-    journalentry 2002-02-28 "User manual completed" {
-      author boss
-      summary "The doc writers did a really great job to finish on time."
-    }
-  }
-
-  task deliveries "Milestones" {
-
-    # Some milestones have customer payments associated with them. We
-    # credit these payments to the 'rev' account.
-    purge chargeset
-    chargeset rev
-
-    task start "Project start" {
-      # A task that has no duration is a milestone. It only needs a
-      # start or end criterion. All other tasks depend on this task.
-      start 2002-01-16
-      # For some reason the actual start of the project got delayed.
-      # We record this, so that we can compare the planned run to the
-      # delayed run of the project.
-      delayed:start 2002-01-20
-      # At the beginning of this task we receive a payment from the
-      # customer. This is credited to the account associated with this
-      # task when the task starts.
-      charge 21000.0 onstart
-    }
-
-    task prev "Technology Preview" {
-      depends !!software.backend
-      startcredit 31000.0
-      note "All '''major''' features should be usable."
-    }
-
-    task beta "Beta version" {
-      depends !!test.alpha
-      charge 13000.0 onstart
-      note "Fully functional, may contain bugs."
-    }
-
-    task done "Ship Product to Customer" {
-      # The next line can be uncommented to trigger a warning about
-      # the project being late. For all tasks, limits for the start and
-      # end values can be specified. Those limits are checked after the
-      # project has been scheduled. For all violated limits a warning
-      # is issued.
-      # maxend 2002-04-17
-      depends !!test.beta, !!manual
-      charge 33000.0 onstart
-      note "All priority 1 and 2 bugs must be fixed."
-    }
-  }
-}
-