Issue Types, States & Priorities

Every Issue in GreenVee has a state, an optional priority, an optional due date, and an optional type. Understanding these fields helps you track work accurately and keeps workflows moving.

States — the Issue lifecycle

An Issue always sits in exactly one state. Move it forward as work progresses.

Backlog → Todo → In Progress → In Review → Done
   │         │          │            │
   └─────────┴──────────┴────────────┴──→ Cancelled
                                      └──→ Duplicate

Any active state can move directly to Cancelled or Duplicate — you do not have to reach In Review first.

State	Meaning
Backlog	Raised but not yet prioritised for action
Todo	Confirmed and ready to work on
In Progress	Actively being worked on
In Review	Work done, waiting for sign-off or verification
Done	Resolved and closed
Cancelled	No longer relevant — closed without resolution
Duplicate	Same as another Issue — closed in favour of that one

For Field Workers

When you finish work on an Issue, move it to In Review — not straight to Done. That signals to your team lead that a check is needed before it closes.

Caution

Do not leave Issues in In Progress indefinitely. If work is blocked, add a comment explaining why and consider moving it back to Todo or Backlog so the team lead can see it needs attention.

Priority

The Priority field signals urgency. Set it when you raise an Issue so assignees know what to tackle first.

Priority	When to use it
Urgent	Blocking work right now — needs same-day attention
High	Important, should be resolved this week
Medium	Normal — no hard deadline, but do not let it drift
Low	Nice to resolve, but not blocking anything
(none)	Unclassified — triage as soon as possible

Due date

The Due date field is optional. Use it when an Issue has a hard deadline — for example, a permit approval that must arrive before groundwork begins. Issues with a due date appear highlighted in My Issues when that date is approaching.

Issue types — forward-looking

GreenVee includes an Issue type system designed to connect typed workflow requests directly to the Issue tracker. Every Issue has a type — new Issues you create today are always CUSTOM (a general, untyped Issue). The full set of types the system defines is:

Type	What it will represent
CUSTOM	A general Issue with no specific type — the default for every Issue you create today
APPROVAL	A formal approval request
DECISION	A decision that needs to be recorded
GOOD_PROCUREMENT_REQUEST	A request to procure goods or materials
RISK_ACTION	An action item raised from a risk register
EQUIPMENT_BOOKING	A request to reserve equipment
EMPLOYEE_BOOKING	A request to allocate a person
GOOD_BOOKING	A request to reserve goods or materials for use
CUSTOMER_INQUIRY	An inquiry raised by a customer
COMPANY_INQUIRY	An inquiry raised by or about a partner company
PRE_ENGINEERING_REQUEST	A request related to pre-engineering work
BUDGET_REQUEST	A request for additional or reallocated budget

Forward-looking

The Issue type system is not yet active. Today, requests like Procurement Requests, Budget Requests, and Bookings are created through their own dedicated forms and live in their own records — they do not yet appear as Issues, and there is no way to pick a type when creating an Issue yourself.

When the type system becomes active, these form-based flows will automatically generate typed Issues. Approvals, requests, and workflow asks across GreenVee will surface in one place — the Issue tracker. Nothing will change about how you submit those forms; the system will handle the connection in the background.

For now, every Issue you create manually is type CUSTOM. It has no effect on how an Issue behaves today.