CommunesPlone requirements

• a task creator : the user creating the task
• a description : presenting the task
• an activated date : the date the task will be shown to the "user"
• a start date : the date the user indicates he begins the task
• an expected end date : the date the task must be normally achieved
• an end date : the date the "user" will close the task
• a category : informative category
• a priority : an importance indicator
• a sequence of tasks : a suite of linked tasks
• a weight : a weight indicator permitting the progress calculation in a sequence of tasks
• a task responsible : a person or group responsible of the task
• a performer : a person or group of persons to which the task is assigned
• a performer backup : a person or group of persons to which the task is assigned in case the first performer can do the task
• an initiator : the element initiating the task
• a followup: like in Poi, it should be possible to add followups to the task to provide feedback about the progress an to track changes in the task (new responsible, changed due date)
  

A global requirement for all our products is the flexibility and user friendly configuration. The product has to propose a "plone site" by "plone site" configuration possibility because the product is used on the same zope instance but on different plone sites.

Some attributes must be optional and activated in the tool. The categories, priorities, ... must be defined in the tool. The performer type must be defined in the tool.

A task can be linked to another object or tasks. A task can be activated (showed to the performer) by an "event" (manual action or automated action). A user can see his tasks, be warned by mail. A task must appear in the calendar.