BACKLOG: Backlog item
A product backlog item for requirements management with prioritisation, sprint assignment, and WSJF scoring.
Default definition. This article describes the default
BACKLOG 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 BACKLOG.Entity properties
| Property | Value |
|---|---|
| Entity code | BACKLOG |
| Display name | Backlog item |
| Plural | Backlog items |
| Level | 540 |
Use cases
BACKLOG is the product backlog entity for capturing and prioritising requirements 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
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Title. Placeholder: As a [user], I want [feature] so that [benefit]. |
type | singleselect | Yes | Type. |
priority | singleselect | Yes | Priority. |
status | singleselect | Status. | |
us | reference → USA | Item. | |
sprint | reference → SPRINT | Sprint. |
General: Planning
| Field | Type | Required | Notes |
|---|---|---|---|
story_points | number | Story Points. | |
business_value | number | Relative business value (1-100) | |
wsjf_score | number | Read-only. Weighted Shortest Job First score | |
estimated_hours | number | Estimated Hours. | |
actual_hours | number | Actual Hours. |
General: Description
| Field | Type | Required | Notes |
|---|---|---|---|
description | text (multi-line) | Detailed description of the requirement | |
acceptance_criteria | text (multi-line) | Acceptance Criteria. Placeholder: Given [context], When [action], Then [outcome]. | |
requiredBy | text | Require by. |
Activity: Assignment & Dates
| Field | Type | Required | Notes |
|---|---|---|---|
product_owner | reference → user | Product Owner. | |
assigned_to | reference → user | Assigned To. | |
team | reference → TEAM | Team. | |
reporter | reference → user | Reporter. | |
due_date | date | Due Date. | |
start_date | date | Start Date. |
Activity: Categories & Labels
| Field | Type | Required | Notes |
|---|---|---|---|
epic | reference → BACKLOG | Parent epic this item belongs to | |
component | reference → COMPONENT | Component. | |
release | reference → RELEASE | Target Release. | |
project | reference → PROJECT | Project. | |
labels | text | Labels. Placeholder: Comma-separated labels. |
Activity: Technical Details
| Field | Type | Required | Notes |
|---|---|---|---|
technical_notes | text (multi-line) | Technical Notes. | |
definition_of_done | text (multi-line) | Definition of Done. Placeholder: Checklist of completion criteria. |
Attachments
| Field | Panel | Allowed types | Max files |
|---|---|---|---|
attachments | Attachments | .pdf, .doc, .docx, .xls, .xlsx, .png, .jpg, .jpeg, .gif | multiple |
Relationships
- Lookups:
uspoints at aUSArecord;sprintpoints at aSPRINTrecord;teampoints at aTEAMrecord;epicpoints at aBACKLOGrecord;componentpoints at aCOMPONENTrecord;releasepoints at aRELEASErecord;projectpoints at aPROJECTrecord. - Related lists:
BACKLOG,BACKLOG,BACKLOG,TESTCASE,SUPPORTTICKET. - Activity: activity timeline panel attached.
Creating a Backlog item via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "BACKLOG",
"level": 540,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Title",
"type": "Type",
"priority": "Priority",
"description": "User Story / Description"
}Listing Backlog items records
GET /v1/entities/BACKLOG/SUB