DemandFlow Support Centre

BACKLOGP: Project task

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A project backlog item for requirements management with prioritisation, sprint assignment, and delivery.

BACKLOGP: Project task

A project backlog item for requirements management with prioritisation, sprint assignment, and delivery.

Default definition. This article describes the default BACKLOGP 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 BACKLOGP.

Entity properties

PropertyValue
Entity codeBACKLOGP
Display nameProject task
PluralProject tasks
Level540

Use cases

BACKLOGP is the product backlog entity for capturing and prioritising requirements specific to a project before they enter a sprint. It supports multiple item types (User Story, Feature, Task, Bug, Technical Debt, Spike) making it a general-purpose requirements container. The WSJF (Weighted Shortest Job First) score field supports SAFe-style prioritisation alongside story points and business value. Items can be linked to a user story (USA entity via objectLookup with comboKey 3) when promoted to active work.

Fields

General: Basic Information

FieldTypeRequiredNotes
nametextYesTitle. Placeholder: As a [user], I want [feature] so that [benefit].
typeenumYesType. Valid ids: 1 (Task), 2 (User Story), 3 (Epic), 4 (Feature), 5 (Bug).
assignedreference → userAssignee.
priorityenumYesPriority. Valid ids: 1 (Low), 2 (Normal), 3 (High), 4 (Critical).
statusworkflowStatusStatus.
epicreference → BACKLOGPEpic.
sprintreference → SPRINTPSprint.

General: Planning

FieldTypeRequiredNotes
pointsnumberPoints.
business_valuenumberRelative business value (1-100)
wsjf_scorenumberRead-only. Weighted Shortest Job First score (Business Value / Story Points)
estimated_hoursnumberEstimated Hours.
actual_hoursnumberActual Hours.

General: Description

FieldTypeRequiredNotes
descriptiontext (multi-line)Detailed description of the requirement
acceptance_criteriatext (multi-line)Acceptance Criteria. Placeholder: Given [context], When [action], Then [outcome].
requiredBydateRequired by.

Activity: Assignment & Dates

FieldTypeRequiredNotes
product_ownerreference → userProduct Owner.
assigned_toreference → userAssigned To.
teamreference → TEAMTeam.
reporterreference → userReporter.
due_datedateDue Date.
start_datedateStart Date.

Activity: Categories & Labels

FieldTypeRequiredNotes
epicreference → BACKLOGParent epic this item belongs to
componentreference → COMPONENTComponent.
releasereference → RELEASETarget Release.
projectreference → PROJECTProject.
labelstextLabels. Placeholder: Comma-separated labels.

Activity: Technical Details

FieldTypeRequiredNotes
technical_notestext (multi-line)Technical Notes.
definition_of_donetext (multi-line)Definition of Done. Placeholder: Checklist of completion criteria.

Attachments

FieldPanelAllowed typesMax files
attachmentsAttachments.pdf, .doc, .docx, .xls, .xlsx, .png, .jpg, .jpeg, .gifmultiple

Relationships

  • Lookups: epic points at a BACKLOGP record; sprint points at a SPRINTP record; team points at a TEAM record; epic points at a BACKLOG record; component points at a COMPONENT record; release points at a RELEASE record; project points at a PROJECT record.
  • Related lists: BACKLOG, BACKLOG, BACKLOG, TESTCASE.
  • Activity: activity timeline panel attached.

Creating a Project task via the API

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

{
  "entity":   "BACKLOGP",
  "level":    540,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Title",
  "type": "1",
  "priority": "1",
  "description": "User Story / Description"
}

Listing Project tasks records

GET /v1/entities/BACKLOGP/SUB

See also

backlogpproject taskproject tasksbacklog

Was this article helpful?

← Back to Knowledge Base