Day-to-Day Work
Issues vs Tasks
Understand when to use an Issue and when to use a Task — the most important distinction in GreenVee.
GreenVee has two types of work items: Tasks and Issues. They look similar at first glance, but they serve very different purposes. Choosing the right one keeps your project timeline accurate and your workflows clean.
The rule of thumb
Section titled “The rule of thumb”Tasks for scheduled work on the plan. Issues for everything that needs a state machine — approvals, requests, problems, todos.
Side-by-side comparison
Section titled “Side-by-side comparison”| Task | Issue | |
|---|---|---|
| What it represents | A scheduled piece of work in the project plan | A ticket that needs to move through a workflow |
| Lives on the timeline? | Yes — has a start date, duration, and position on the Gantt | No — belongs to a Project but not to any segment or timeline |
| Assigned to | A Project Member (a person in a specific project role) | A User Account (any GreenVee user) |
| State machine | Same states as Issue: Backlog → Todo → In Progress → In Review → Done (or Cancelled / Duplicate) — but a Task’s state doesn’t drive the schedule; its dates come from the timeline | State machine: Backlog → Todo → In Progress → In Review → Done (or Cancelled / Duplicate) |
| Typical examples | “Pour foundation slab”, “Install electrical conduit”, “Complete safety inspection” | “Approve material substitution”, “Request extra budget”, “Report site hazard”, “Book equipment” |
Worked examples
Section titled “Worked examples”Scenario 1 — Building phase
Your project plan has a line item called “Build foundation”. A crew member is assigned to it, it starts on Monday, and it takes five days. This is a Task. It sits on the Gantt chart inside the relevant project segment.
Scenario 2 — Material substitution
The specified concrete mix is unavailable. Someone raises a ticket to get an alternative approved. It needs to go from “raised” → “under review” → “approved” before work can continue. This is an Issue. It has a state, an assignee (the person responsible for chasing approval), and optionally a due date.
Scenario 3 — Equipment booking
A site manager needs a specific piece of equipment reserved for next week. They submit a request that goes through an approval step. This is an Issue (specifically one that will eventually be typed as EQUIPMENT_BOOKING).