Projects and Project Tasks
On this page
- Projects and project tasks in the Web App
- Projects and tasks in the supplied configuration
- Create a project
- Add tasks, milestones, and sub-tasks
- Plan and schedule a task
- Assign a task and log work
- Begin, complete, close, and reopen a task
- Complete, close, and reopen a project
- Suggest a project's scheduled dates
- What Auto Scheduled does
- When Start Overdue and Completion Overdue are set
- Completion timing values
- Related topics
A project holds a tree of project tasks. A project can have subprojects, and a task's parent is always either a project or another task, never empty.
A project task carries a planned schedule and an actual one: planned start and end dates and planned effort beside actual start and end dates and time spent. A task always has a planned start date: when none is given, it is today. A project has the same shape at its own level, with scheduled and actual start and end dates, planned effort, and cumulative time spent. A project's planned effort and cumulative time spent are read-only; you do not type them.
The product itself defines one status for projects, Closed. Project tasks have Closed, In Progress, and Completed. All other statuses, and the actions that move a project or task between them, come from the workflow configuration; see Workflow Overview. An action marked as a reopen action is offered only while the record is in its Closed status. A project in its Closed status is not offered in a record's project field or as another project's parent.
Projects and project tasks in the Web App
In the Web App's sidebar, the entries for projects and for project tasks are in the Project Management group. Not every technician sees every entry of the sidebar.
View tasks: List, Gantt, and Board
A project's Tasks tab holds three views of the same tasks, switched with the List, Gantt, and Board buttons. The tab opens on List.
- List shows the tasks as a tree, with an Actions button and a New Task button, which is hidden while the project's form is read-only. Its default columns are the task's flag, ID, number, summary, milestone flag, assignee, and status. The list has no filter bar and no choice of views; the same holds for a task's Sub-Tasks tab.
- Gantt shows the tasks as a chart; see the next section.
- Board shows the tasks as a kanban board, with its own Add button.
Work in the Gantt chart
The chart's grid has the columns number, name, assignee, start, and finish. The assignee cell shows the person's picture beside the name. A start or finish cell is blank when the task has no date for it; otherwise it shows the date and, when there is one, a second line with the offset against the plan.
The chart's toolbar offers:
- New, which lists the ways your workflow provides to add a project task to the project. It is enabled only when you have the right to edit both the project and project tasks. When the workflow provides none, the menu holds a single item saying that there are no actions.
- Actions and Delete.
- Indent and outdent commands, which change a task's parent without dragging. Each is enabled or not depending on the task's place in the tree.
- A toggle that expands or collapses all rows at once.
- Fit and refresh commands.
- Today, zoom-in, and zoom-out commands, and a date picker.
To reorder or re-parent a task, drag its row in the grid. Dropping it after another task places it under that task's parent; a drop that targets no task leaves the parent as it was. The change is saved at once. The drop takes effect only while the pointer is over the grid or its header. The bars on the chart cannot be dragged or resized, and their progress cannot be dragged.
Right-click a task's row in the grid, or click the row's tree icon, to open the task's menu; right-clicking a bar opens no menu. Its New Sub-Task section lists the ways your workflow provides to add a task under this one; its Actions section lists the task's available workflow actions. Double-clicking a task's row opens the task's own record; double-clicking a bar does nothing.
A bar's color reflects its schedule. A scheduled task is a green bar, with the completed part in a darker green. A task without a schedule, or with an invalid one, is an orange bar; whether a schedule is valid is decided by comparing the task's planned dates with the span of its sub-tasks. A milestone is a blue marker. The dark theme draws the bar and its completed part in darker shades. No separate color shows whether a task is open, in progress, or completed.
Run the embedded step action
The Gantt chart offers one embedded step action of project tasks as a command on the card of a task's bar. To run it on a task:
- On the project's Tasks tab, click Gantt.
- Hover over the task's bar on the chart. A card opens.
- At the bottom of the card, click the command, which shows the action's icon and caption. The action runs on the task and opens its form.
The command is dimmed and cannot be clicked when your security roles do not grant the action, or when the task's type or status is outside the types and statuses the action allows. Only the first embedded step action of project tasks appears on the chart; a second one is never shown there. The action itself is set up in the workflow configuration; see Configure the embedded Step Action of Project Tasks.
See project tasks on the Team Calendar
The Team Calendar is the last entry of the sidebar's Calendars group, which sits directly below the My Work group.
The Team Calendar is a timeline with one row per technician. Two toggles, Project Tasks and Work Orders, decide which of the two the calendar draws. The toggles are remembered in your browser. With both on, the filter sidebar has a Project Tasks section and a Work Orders section; for project tasks it offers project, task type, and task status filters.
The technician rows come from the calendar's assignee filter and its Group filter. Every person checked in the assignee filter becomes a row. Every group checked under Group adds a row for each active technician in that group, not for every member. The Group filter lists only active groups that are flagged for technicians only. A person appears in one row even when checked through both filters.
A project task's bar runs from its actual start date, or its planned start date if it has none, to its actual end date, or its planned end date if it has none. The bar is titled with the task's ID in brackets followed by its name. Hovering the bar shows a card with the task's class and ID, its caption, its assignee, its start and, when it differs, its end, and its status when it has one. The bar's right-click menu, and the card's footer, offer commands to open the task, in the current tab or in a new one, and to show its details. A project task's bar cannot be dragged to reschedule the task.
For the calendar's other pages and features, see Calendars.
A project's fields and tabs
A project's General tab has three groups:
- Details: the project's name, data segment, type, tags, manager, organization, and calendar. The calendar is chosen from shared calendars; personal calendars are never offered. See Work Calendars.
- Dates: the scheduled start and end dates and the start and end dates.
- Performance: planned effort, cumulative time spent, percent complete, and closure code.
A project's percent complete is a whole number from 0 to 100. The database does not roll it up from the project's tasks: it holds whatever a workflow action or a technician writes.
A project's cumulative time spent includes the time of activities logged on the project and on its descendant tasks. It is recalculated when tasks are moved to another parent or their time spent changes.
Besides General, a project has the Tasks tab, described below, and the tabs Activity, Custom Data, Tickets, Related Objects, Notes, History, and Attachments. On a project, Activity is a tab of its own, not part of the General tab.
A task's fields and tabs
A project task's General tab has two groups, with the task's description and its activity in the right column:
- Details: the task's summary, data segment, type, priority, assignee, tags, parent, and milestone flag.
- Schedule: Auto Scheduled, deadline, planned start and end dates, actual start and end dates, planned effort, percent complete, completion timing, time spent, and the Start Overdue and Completion Overdue boxes.
Auto Scheduled is selected on a task until you clear it. A task's percent complete is a whole number from 0 to 100; as with a project, the database does not calculate it.
Time is recorded on activities. A task's time spent is the time of its own activities plus the time of the activities of every task below it. Deleting an activity recalculates the time spent without it.
The completion timing is written automatically whenever a task is saved, from whether the task has started and, once it has, how its actual start compares with its planned start. The values it takes come from the workflow configuration; see Completion timing values.
A task's other tabs are Sub-Tasks, Custom Data, Related Objects, Notes, History, and Attachments. The Sub-Tasks tab shows the task's sub-tasks in the same tree as the project's task list, described next.
On both forms, the Custom Data tab is shown only when custom fields are placed on that tab; without them, the form has no such tab.
Projects and tasks in the supplied configuration
A new database created with the Default Workflow contains the workflow actions and business rules for projects and project tasks that this section describes. A database upgraded from an earlier version need not contain them, and an administrator may have changed them. See Default Workflow Configuration.
On the Gantt chart, a task's available workflow actions are listed in the Actions section of the task's menu, and the create actions for tasks are listed in the New menu and in the New Sub-Task section of the task's menu.
Create a project
Two actions create a project interactively:
- New Project, captioned Project, opens the form Create a Project. The name and type are required; the organization, manager, and scheduled start and end dates are optional.
- New Project Plan, captioned Project Plan, is a wizard that creates the project and its first tasks in one pass. It asks for the project's name, type, organization, manager, and scheduled dates, which default to one week and three weeks ahead, and has up to ten Task Name fields.
A third create action, API Project Creation, is granted to every role, and nothing in the supplied configuration hides it from the list of create actions.
The project action Copy Project copies the project's tasks along with it.
Add tasks, milestones, and sub-tasks
The create actions for project tasks include New Task, New Milestone, and New Sub-Task.
A milestone is a task whose planned end is its planned start. New Milestone requires a project and a planned start. It sets the planned end date to the planned start date, and the planned effort and the percent complete to 0. It sets the status to Assigned only when you give an assignee.
Create Sub-Task creates a task under the current task. It is offered in Unassigned, Assigned, In Progress, and On Hold, and not on milestones. It requires a Summary and a Planned Start Date, which defaults to the current task's planned start date.
Copy Task copies a task; its form includes Auto Scheduled, taken from the task being copied.
Plan and schedule a task
- Plan Task, which is not offered on milestones, requires a Planned Start Date and offers Planned End Date, Planned Effort, Comment, and Time Spent. It records the activity "Task was Planned".
- Schedule, offered in Unassigned, Assigned, In Progress, and On Hold, asks for the assignee, the planned dates, the planned effort, and the deadline. On a milestone, it sets both planned dates to the start date. Depending on the case, it records the activity "Task was assigned" or "Task was scheduled" and, after validating the primary e-mail address, sends an e-mail notification. Schedule is also the embedded step action: on the Gantt chart, it is the command at the bottom of the card of a task's bar.
- Place On Hold, offered in Assigned and In Progress, opens the form Provide a Reason and sets On Hold. Take Off Hold is offered only in On Hold.
Assign a task and log work
- Assign to me makes you the task's assignee and sets Assigned. Assign to... requires an assignee, sets Assigned, and, after validating the primary e-mail address, sends an e-mail notification. Neither is offered on a milestone.
- Log Work is offered only when you are the task's assignee. Its form, Log your Work, requires a Comment and a Percentage Complete, which starts at the task's current percent complete, and offers Time Spent. The action records the activity "Work was logged", writes the percentage to the task, and notifies the task's followers and collaborators. Further steps of the action, each under its own condition, set the task to In Progress and update the parent project.
- Automatic Timer On and Automatic Timer Off are offered on a task only in Assigned and In Progress. Automatic Timer On is offered while the timer is off, asks only for an optional Comment, and records the activity "Automatic Timer was Turned On". Its form reminds you: "NOTE: Remember to turn the automatic timer off to avoid incorrect time spent entries." Automatic Timer Off is offered while the timer runs and records the activity "Automatic Timer was Turned Off" with the minutes since the timer was turned on as its time spent, which then counts toward the task's time spent.
Begin, complete, close, and reopen a task
- Begin Task is offered in every status and sets the actual start date to the current time each time it runs, also when the task already has an actual start date. It does not change Start Overdue or Completion Overdue.
- Complete Task, offered in Assigned and In Progress, records the activity "Marked as 'Completed'", sets Completed, fills the actual start date and the actual end date with the current time where they are still empty, sets the percent complete to 100, and notifies the task's collaborators. A task that already has an actual start date keeps it.
- Mark Duplicate fills the same two dates and sets Closed.
- Close Task is offered only in Completed and does not ask for a closure code. It records the activity "Marked as 'Closed'", sets Closed, and sends a notification.
- Reopen Task, a reopen action offered only in Closed, writes the percent complete from its form, sets Assigned, and clears the actual end date, Start Overdue, and Completion Overdue. The actual start date stays. None of the supplied actions clears a task's actual start date.
Complete, close, and reopen a project
- Mark Started, offered in Pending, sets the project's status and its start date.
- Mark Completed, offered in In Progress, asks for an End Date and sets Completed.
- Close Project is offered only in Completed and offers the closure code as optional. It records the activity "Marked as 'Closed'", sets Closed, and sends a notification.
- Reopen Project, a reopen action offered only in Closed, sets Pending and clears the project's start and end dates.
Mark Completed sets Completed whatever the state of the project's tasks, and neither it nor Close Project or Reopen Project changes the tasks: completing, closing, or reopening a project leaves its tasks as they are.
Suggest a project's scheduled dates
Suggest Timeframes opens the form Suggest Timeframes, which reads "Please fill in the following fields." It shows Scheduled Start and Scheduled End, the project's scheduled dates, beside Suggested Start and Suggested End, all four read-only, and offers Comment and Time Spent. The suggested start is the earliest planned start date, and the suggested end the latest planned end date, of the tasks directly under the project that are not in the Closed status; their hints read "Date based on the earliest scheduled task." and "Date based on the latest scheduled task." Submitting the form always writes both suggested dates into the project's scheduled start and end dates and records the activity "Timeframes Suggested".
What Auto Scheduled does
Business rules act on a task's Auto Scheduled box:
- When you select the box, the task's planned start and end dates move to the earliest planned start and the latest planned end of its child tasks. A task without child tasks keeps its own dates.
- When a task is saved with a changed planned start date, planned end date, or parent, or moves into or out of Closed, its parent task's planned dates are recalculated from the planned dates of the task, unless it is closed, and of its sibling tasks. This happens only when the box is selected on the parent task; a parent task whose box is cleared keeps its dates.
- When a task moves to another parent or is deleted, its former parent task is recalculated in the same way from the tasks that remain under it.
A project's dates do not follow its tasks.
When Start Overdue and Completion Overdue are set
Two business rules run every 15 minutes over tasks that are neither Closed nor Completed:
- Start Overdue is selected on a task that has no actual start date and whose planned start date lies at least the grace period in the past. The grace period is the workflow parameter Project Task Grace Period for Overdue Start (Hours), which is set to 24 in the supplied configuration.
- Completion Overdue is selected on a task that has no actual end date and whose planned end date lies at least one minute in the past.
When Complete Task fills in an actual date, the matching box is decided again by comparing that date with the plan, so completing a task within its plan clears a box that a rule had selected.
Completion timing values
The completion timing that is set whenever a task is saved takes one of four values in the supplied configuration:
- Unstarted while the task has no actual start date.
- On Time when the actual start is at the same minute as the planned start or, for a planned start without a time of day, on the same day.
- Ahead when the task started earlier than planned.
- Delayed when the task started later than planned.