Reference
Issue Types
Reference for all Issue type codes defined in GreenVee's data model, with notes on current product availability.
What is an Issue type?
Section titled “What is an Issue type?”An Issue in GreenVee is a trackable work item or problem. Every Issue has a state (backlog → todo → in progress → in review → done / cancelled / duplicate) and a type that classifies what kind of issue it is — defaulting to a general CUSTOM type until a more specific one applies.
The type system exists so that Issues of different kinds can be handled consistently — routed to the right people, displayed with the right fields, and connected to the right workflows. Today, each equivalent record is managed through a dedicated form; in the future, the Issue tracker will unify them.
Issue Type Reference
Section titled “Issue Type Reference”| Type code | Plain-English meaning | What record handles this today |
|---|---|---|
| CUSTOM | A general, ad-hoc work item that doesn’t map to a specific business process — the default type for an Issue. | Standard Issue, handled like any task-like work item. No dedicated form. |
| APPROVAL | A request for a formal sign-off or authorisation on a decision, deliverable, or document. | Ad-hoc — managed through comments, documents, or external tools. |
| DECISION | A formal decision that needs to be made and recorded — e.g. which approach to take, whether to proceed. | Decision records (standalone, under Risk & Governance). |
| GOOD_PROCUREMENT_REQUEST | A request to procure a specific Good or material for the project. | Procurement Request form (Materials & Equipment area). Schema: good_procurement_request. |
| RISK_ACTION | An action to be taken in response to a Project Risk — to mitigate, accept, or exploit it. | Risk Action records, attached directly to a Project Risk. Schema: risk_action. |
| EQUIPMENT_BOOKING | A request or confirmation to reserve a piece of Equipment for use on a project or task. | Equipment Booking form (People & Time or Equipment area). |
| EMPLOYEE_BOOKING | A request or confirmation to allocate an Employee’s time to a project or task. | Employee Booking form (People & Time area). |
| BUDGET_REQUEST | A request to increase, create, or adjust a Budget line. | Budget Request form (Money area). |
Issue States
Section titled “Issue States”Regardless of type, all Issues move through the same state machine:
| State | Meaning |
|---|---|
| Backlog | Recorded but not yet scheduled. |
| Todo | Acknowledged and queued for action. |
| In Progress | Someone is actively working on it. |
| In Review | Work is done; awaiting sign-off or verification. |
| Done | Resolved and closed. |
| Cancelled | No longer needed; closed without resolution. |
| Duplicate | Found to be the same as another Issue; closed with a reference to the original. |
What will change when Issue types are activated?
Section titled “What will change when Issue types are activated?”When the type system goes live:
- Procurement Requests, Budget Requests, Employee Bookings, and Equipment Bookings will each appear as typed Issues in the Issue tracker alongside other work items.
- You will be able to filter Issues by type to see, for example, all open Procurement Requests on a project.
- Each type may surface different fields in the Issue detail view — a
GOOD_PROCUREMENT_REQUESTwill show Good and quantity fields; aRISK_ACTIONwill show the linked risk. - Existing records created through today’s dedicated forms will be migrated or linked automatically.
Until then, use the dedicated forms for each record type and refer to this page only as a guide to GreenVee’s intended direction.