What are work items?

Work Items

A work item is any unit of work your team needs to plan, track, and complete. A work item can be as large as a full client project or as small as a one-off bug fix. Below is an example of work item whose type is Project:

Work items can be nested inside one another to form a hierarchy, for example Project → Task → Sub-Task. You can nest as many levels as you need. Below is an example of some deeply nested work items that live inside the Project named Client Web Application:

What a Work Item Can Include

People and scheduling

  • Assignees: One or more people responsible for the work
  • Dates: When the work should start and finish
  • Dependencies: Other work items that must be finished first
  • Repeating schedule: Work items can repeat, which is useful for recurring work like monthly reports or weekly check-ins

Custom fields

  • Add as many custom fields as you need to capture the details that matter to your organization
  • Use formula fields to calculate values from other fields automatically

Visibility

  • A work item can be public or private

Financials

  • Budgets: Planned time or cost
  • Planned fees, planned profit, and planned profit margin: Track a work item’s expected financial performance before the work begins
  • Billing: Mark work as billable so it can be invoiced

Mixed Billing

A single billable work item can combine more than one billing method. For example, a project might include:

  • Fixed fee work items, which are billed at an agreed price
  • Time & materials work items, whose billable fees build up from billable time logs and billable expenses
Website Redesign             (Billable Project)
├── Discovery & Strategy     (Fixed Fee)
├── Design & Build           (Fixed Fee)
└── Ongoing Support          (Time & Materials)

Each part of the work is billed the way your agreement with the client calls for.

The screenshot below shows the Accounting tab section on the work item setup form. This is where you can specify the Financial Budget and more.

Templates

Templates let you reuse work you’ve already structured instead of building it from scratch each time.

  • Create from a template: Start a new work item from a template, along with its structure and details.
  • Inject a template: Add a template into an existing work item. This is useful when the scope grows or a standard set of tasks needs to be added partway through.

Proposals

You can build proposals directly from work items, so the scope, structure, and planned fees you’ve set up flow straight into what you send to the client.

Work Item Types

Every work item has a type that describes what kind of work it is. To get you started, Ravetree includes two standard types, Project and Task. You can modify or remove them, and create as many of your own types as you need (for example, Bug, Support Ticket, Sprint, or Milestone).

Each type can have its own:

Setting What it controls
Name How the type appears throughout Ravetree
Icon and Color How work items of this type look in lists, boards, and timelines
Fields Which details appear on the work item, and which are required
Workflow The statuses a work item moves through, from start to completion

Types let you shape Ravetree around how your organization works:

  • Use your own terminology. Name types the way your team already talks. For example, an agency might call a project a Job.
  • Turn on only the features you need. For example, you might turn off accounting features on a Bug type, because bugs are tracked internally and never invoiced.

Default type: One type is marked as the default. It’s pre-selected whenever someone creates a new work item.

Changing a type: You can change an existing work item’s type at any time.

Nested Work Items

There’s no limit to how many levels deep you can nest work items. Ravetree uses the terms below to describe how nested work items relate to each other.

Term Meaning
Parent A work item that directly contains one or more other work items
Child (or sub work item) A work item nested directly inside another
Root The top-level work item in a nested tree. It has no parent.
Descendants Every work item nested inside a given work item, at any depth
Ancestors Every work item that contains a given work item, up to the root
Path The ordered list of a work item’s ancestors, from the root down. It’s often shown as breadcrumbs.

Example

Website Redesign          (Project)
└── Build Homepage        (Task)
    └── Write Hero Copy   (Sub-Task)

From the point of view of Build Homepage:

  • Its parent is Website Redesign.
  • Its child is Write Hero Copy.
  • Its root is Website Redesign.
  • Its ancestors are Website Redesign.
  • Its descendants are Write Hero Copy.
  • Its path is Website Redesign › Build Homepage.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.