Incident

Affects (Procedure), postmortem links and Source Intake are real relationships. Accountable and About fields are text. Record impact dates, severity, response plan and root cause when known. Link the postmortem to Content or Change Decision. The model calls for a write-up for closed High incidents, but nothing enforces it automatically.

Use and boundaries

Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.

Related guide · All entities

Fields

Field	Storage	Source, options or boundary
Name	Text	Stored value.
Description	Long text	Stored value.
Severity	Single select	High, Medium, Low
Affects (Tool)	Text	Text reference; not a linked record.
Affects (Procedure)	Linked records	Procedure
Affects (Organization)	Text	Text reference; not a linked record.
Root Cause	Long text	Stored value.
Postmortem (Change Decision)	Linked records	Change Decision
Postmortem (Content)	Linked records	Content
Response Plan	Long text	Stored value.
Start Date	Date	Stored value.
End Date	Date	Stored value.
About (Person)	Text	Text reference; not a linked record.
About (Organization)	Text	Text reference; not a linked record.
About (Membership)	Text	Text reference; not a linked record.
Accountable	Text	Text reference; not a linked record.
Source Intake	Linked records	Intake
Tags	Linked records	op:tags · optional labels from the Core Tags catalog; classification only.

Example and maintenance

Illustrative example: a failed collection has impact dates, a response plan and a linked postmortem.

Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.