Skip to main content

Core concepts

DevRev bridges silos by connecting three core objects: identity, parts, and work. By connecting work to parts and parts to customer and developer identity, we bring devs closer to their revs.

work types


  • Dev refers to you and your team, the provider of a product or service.
  • Rev refers to your customer, the consumer of the product or service you provide.


A part is a piece of a product and can be made of rev parts and dev parts.

  • Rev parts relate to how a product is consumed by your customers, with three main types: product, capability, and features.
  • Dev parts are the code, service, or components built or used by the developer.
  • Rev parts are often served by one or more Dev Parts.

One of your first experience in the app will be in DevRev trails. Build your trail, create Rev and Dev Parts and connect them to enable your teams to be product-led and customer-centric.

Learn more about creating parts and trails here.


Work is anything that requires activity to be performed by a human or machine; it requires an owner and some level of effort.

A work item is any artifact in the system that requires some activity to be performed by a human or machine. They have associated owners and require some level of effort. Work can commonly be the source of, or lead to other work items. In that sense, work can be linked together and have parent/child relationships. For example, a high-level issue may spawn multiple child issues/tasks which may each have their own owner as well as their own children items.

  • A conversation is a synchronous or near-synchronous discussion that may be escalated to a ticket. Refer to PLuG.
  • A ticket is a work item created by the customer or consumer. Refer to Support.
  • An issue is a work item created by the builder or maintainer. Refer to Build.
  • A task is a work item used to break down larger work into smaller pieces.


A task is a work item that can exist on its own as a singular action or can exist in the context of another work item. Tasks are owned by the owner of the work item. They are used to break down larger work items into near-term activities and to track progress towards work item completion.

Tasks may be created by automatically or by a dev user.


  • Stalled
  • Priority/Escalated
  • Fast/Slow Moving
  • Blocked

The following figure shows the state machine for tasks:

Task state machine