Decision ticket¶
Each planned or ongoing decision should be represented by a Plan.io ticket. The usage of the ticket’s fields and custom fields are outlined in the table below. Where usage varies depending on the stage in the decision pipeline, a detailed description is provided in the Decision Pipeline documentation and this is noted in the table.
All fields listed below are REQUIRED unless stated otherwise.
Field |
Description |
---|---|
Subject |
A short and up-to-date representation of the decision. |
Status |
A description of where the decision is in the decision pipeline, chosen from available decision statuses. |
Parent Ticket |
Main ticket ID where the work to advance the decision is happening. |
Decision Link |
A link to the ticket or poll where the decision is taking place. |
Description |
Emerging decisions or simple decisions at any stage of the pipeline may provide a decision summary in the description field. |
Decision Summary |
A link to a document containing a decision summary. |
Assignee |
The individual or group being notified of the latest update. |
Due Date |
The estimated date that a decision is expected to begin. |
Decision Start Date |
The date that a decision is scheduled to begin. (Scheduled decisions only.) |
Decision End Date |
The date that a decision is scheduled to end. (Scheduled decisions only.) |
Decision Facilitator |
The individual responsible for the decision facilitator role. |
Decision Team |
All members of the decision team. |
Decision Type |
The type of decision-making process that is planned. |
Event (optional) |
The event where the decision is planned to take place, e.g. June 2022 OGM. |
Team Coordination Ticket |
The ticket where the work of progressing the ticket is happening. |
External Communication Ticket |
The ticket where any communication with people outside the decision team is happening |