Understanding Tasks

Tasks can be treated in two ways (actually three).  Tasks can be assigned to any Request or Channel feature that is activated.  A Channel can also be created for "Tasks", creating "TaskNET".  If a Channel is created named "Tasks" (it actually checks the "record is called" field for "Task") - then the task subsystem in that channel is automatically renamed "Subtasks"... to avoid the obvious confusion of names.  So, tasks can be used as part of WorkNET or other channel, tasks can operate as a separate module (channel), called "Tasks", or in combination.

Tasks  can be assigned to any Request or Channel feature that is activated.  Requests which have tasks enabled at both the channel and request level now offer a task list for the request.  This functions in a manner similar to files and calendar items... the top tasks are displayed in the request, with a link to the task subsystem in which all tasks can be listed, and tasks can be added, modified, and deleted.

Like calendar items and files, tasks contain a STATUS field. Up to 32 statuses and colors can be defined for tasks. Tasks also contain a PRIORITY field. PRIORITY is a numeric value indicating the importance of a task. "PRIORITY 1" tasks are considered the highest priority.   For flexibility, this field defaults to "100" when a new task is added - priority, like status, can be changed at any time, and provide a way to "sort" tasks in an order logical to the request.

Tasks also can be assigned to a WORKER - any system user.  The users email address, RSN, or Nicknames  can be specified to assign a user to a task.

A blended task list is available to channel members allowing all the tasks in a channel to be displayed.   Also, a personal-blended list is available, allowing the user to display all the tasks from all requests in the channel which are assigned to him or herself.  These lists are accessed from the light-blue menu bar within the channel.

Of course, workspace options are also available for blended task displays if desired.