Tasks BackOps Creates from Advances, Files, and Event Types

Some tasks on an event are created and kept up to date by BackOps. They track work that already lives elsewhere in the event, so the task list shows that work without anyone copying it in by hand. This page explains where they come from and how they behave.

Where Generated Tasks Come From

Advances. When a module on an advance has task tracking turned on, BackOps creates a task for the advance, a task under it for the module, and one task under the module for each question and each request. They are assigned to the collaborator the advance is for and due on the module's due date. As the collaborator answers and you review, their statuses move through the event's advance status mapping.

Files. Files and deliverables that go through review get tasks whose statuses follow the file's lifecycle through the event's file status mapping: To Do, In Review, Changes Requested, Done, and Archived.

Event details. When an event type tracks its attributes and roles until they are filled, BackOps adds an Event Details task with a task for each section and one under it for each tracked attribute or role. A task completes once its value is filled in, or moves to the Needs Review status until approved when the event type asks for review. These tasks use the advance status mapping. The event type can also set its due date and default assignee.

flowchart LR
    S["Source: advance, file, or event type"] -->|"creates"| T["Generated task"]
    S -->|"progress"| M["Status mapping"]
    M -->|"sets status"| T

Parent tasks take their status from their children, so a module task is done when all of its question and request tasks are.

What You Can and Cannot Change

A generated task shows where it came from. Its source owns its name, status, place in the task tree, and due date, and it cannot be deleted by hand.

• Advance and file tasks open read-only, with a View advance or View file link to the work itself. Advance tasks also cannot be dragged in the list or Kanban, or selected for bulk edit.
• Event details tasks keep those four fields locked, but you can still change their description, priority, assignees, and other details.

To move a generated task along, work on its source: answer or review the advance, review the file, or fill in the event's attribute or role. Turning task tracking off on an advance module or an event type archives its tasks rather than deleting them.

Choose the Statuses They Use

Generated tasks use your event's own statuses. Pick which status each stage maps to on the event's Project Management page, under Settings > General. See task statuses and custom fields.