DemandFlow Support Centre

ISSUE: Issue

ReferenceEntity Reference16/04/2026Updated 16/04/2026
An issue register entry tracking active problems with category, impact assessment, and contingency planning.

ISSUE: Issue

An issue register entry tracking active problems with category, impact assessment, and contingency planning.

Default definition. This article describes the default ISSUE definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches ISSUE.

Entity properties

PropertyValue
Entity codeISSUE
Display nameIssue
PluralIssues
Level55000

Use cases

ISSUE is the project issue register entity, structurally similar to RISK but for problems that have already materialised rather than potential future events. It is linked to projects via comboKey SUB|PJ. Unlike RISK, it omits the probability field (issues have already occurred) and focuses on impact assessment and resolution.

Fields

Issue

FieldTypeRequiredNotes
nametextYesIssue.
descriptiontextDescription.

Impact

FieldTypeRequiredNotes
categoryenumYesValid ids: technical (Technical), financial (Financial), operational (Operational), resource (Resource), legal (Legal), environmental (Environmental).
impactenumYesValid ids: low (Low), medium (Medium), high (High).

Manage

FieldTypeRequiredNotes
contingency_plantextYesContingency Plan.
statusenumYesValid ids: open (Open), closed (Closed), monitoring (Monitoring), resolved (Resolved).
contingency_plantext (multi-line)Contingency Plan.
next_review_datedateNext Review Date.

Relationships

  • No declared relationships in the default definition.

Creating a Issue via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "ISSUE",
  "level":    55000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Example",
  "category": "technical",
  "impact": "low",
  "contingency_plan": "..."
}

Listing Issues

# All records in your tenant
GET /v1/entities/ISSUE/SUB:<your-sub-id>

See also

issueissues

Was this article helpful?

← Back to Knowledge Base