Every task can be assigned a specific task type to help you more easily visualize the work breakdown structure of a project and categorize the unique components of the task. They also help with resourcing needs and determining which team members should be assigned to which tasks.
The task types are:
- Tasks—Items that need to be completed.
- Deliverables—Things that need to be produced (e.g. documents).
- Milestones—Project deadlines, marking the completion of a phase or stage of a project.
- Issues—Bugs or items that need to be resolved.
Once your task types are assigned, you can specify which types your account members can track time against via the Track Time and Expense Against setting. For example, if you select Tasks and Milestones as seen in the image below, users will only be able to track time and expenses against those specific task types.
To learn more about where you can manage tasks and their types, see the Tasks Overview article.
Tasks are items that need to be completed in order to complete the project. They are the building blocks of projects and help team members track the progress of the work, communicate needs, and show which items still need to be completed.
A Deliverable is an item that needs to be produced before the project can move onto the next stage or be completed. Deliverables will vary depending on your project's unique components and can be things such as documents, reports, designs, etc.
For example, the Deliverable task shown below is for a training video. This video must be completed before the project can move onto the next Milestone, which is the release of a new Scheduling feature in the company’s application.
A Milestone marks the completion of a phase in your project timeline or the project itself. You can look at it as a deadline where all required deliverables, tasks, and any applicable issues must be completed or delivered. You can have multiple Milestone tasks within a single project.
All Milestone tasks are highlighted in gray in the Task Tracker to help you quickly locate them and get an overview of how many remaining Milestones the project has.
You can assign weighting to milestones to define percentages of completion at different stages of the project. Milestone weighting is especially helpful for projects where payments are tied directly to achieving certain milestones during the project lifecycle.
To learn more, see the Milestone Weighting article.
Issues are action items that weren’t part of the original project plan, but impact the duration of a project. An Issue may be a software bug, an addition to scope that needs to be discussed, a ticket, or a request. Unlike Tasks, Deliverables, and Milestones, Issues have their own statuses.
Creating an Issue
Since Issues are visible to service providers and Clients, they are a valuable tool for managing any client feedback or capturing client requests. After Issues are created, you can turn them into an action item by changing their type into a task or deliverable.
If you’re reporting a bug or something that needs to be fixed, it’s helpful to be descriptive about the problem you’re experiencing and how your experience is different than what you expected. Here’s an example format:
- Issue Title—A brief description of the problem.
- Steps to Reproduce—The order of actions that led you to the problem.
- Expected Behavior—How you think it should work.
- Actual Behavior—How it actually worked.
Issues come with a unique set of statuses to capture the various resolutions and stages it goes through at different points. An Issue’s status can be updated in the Task Tracker, Gantt Chart, or Task Details side panel.
These statuses are:
- New : This is the default state of a newly created Issue. This status means that an Issue is not in progress. Selecting this status sets the percent complete to 0% (unless the Issue is a parent Issue, in which case the percent complete will roll-up from the subtasks or Issues).
- Reopened : This status indicates when an Issue was previously in a resolved state, but then had to be reinvestigated. Selecting this status sets the percent complete to 0% (unless the Issue is a parent Issue, in which case the percent complete will roll-up from the subtasks or Issues).
- In Progress : This status indicates that an Issue has been assigned to someone and is being worked on.
- Blocked : This status indicates that the assignee is unable to make progress on an Issue (e.g. due to needing additional information).
- Fixed : This status indicates that the Issue has been fixed, but not verified (i.e. not yet resolved).
- Duplicate : This status indicates that there are two or more Issues created for the same problem. Selecting duplicate sets the percent complete to 100% (unless the Issue is a parent Issue, in which case the percent complete will roll-up from its subtasks).
- Can’t Repro : This status indicates that the assignee is unable to replicate the Issue. Selecting this status sets the percent complete to 100% (unless the Issue is a parent Issue, in which case the percent complete will roll-up from its subtasks).
- Resolved : This status indicates that the fix has been verified, and is the default completion status for Issues. Selecting this status sets the percent complete to 100% (unless the Issue is a parent Issue, in which case the percent complete will roll-up from its subtasks).
- Won’t Fix : This status indicates that—after evaluation—a decision has been made not to fix the issue. This status sets the percent complete to 100% (unless the Issue is a parent Issue, in which case the percent complete will roll-up from its subtasks).