USA: User Story
An alternative user story board variant with story points, business value scoring, and SUBTASKA subtasks.
USA 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 USA.Entity properties
| Property | Value |
|---|---|
| Entity code | USA |
| Display name | User Story |
| Plural | User Stories |
| Level | 510 |
Use cases
An alternative user story board variant with story points, business value scoring, and SUBTASKA subtasks.
USA is a variant of the US (User Story) entity for a different kanban board context. The key differences from US are: subtasks use SUBTASKA (linked via comboKey SUB|KBN|USA|ENT which includes kanban board and entity scoping), it includes Fibonacci-sequence story points (0.5 through 89) for estimation, a business value field for prioritisation, and a subtaskCount readonly field that tracks child task count. The comboKey format SUB|KBN|USA|ENT enables subtask scoping per board and entity, which is more granular than US's simpler SUB|US format. Like US, it supports kanban and grid views, board preloading, AI context, and a dynamicform for board-specific custom fields. The description placeholder uses the standard user story template format. Stories link to projects (PJ), epics (EPIC), and sprints (SPRINT) for planning alignment.
Fields
Story Details
| Field | Type | Required | Notes |
|---|---|---|---|
ref | text | Reference. Read only. | |
name | text | Yes | Story title. |
status | kanbanStatus | Yes | Status. |
priority | enum | Yes | Valid ids: 1 (Critical), 2 (High), 3 (Normal), 4 (Low). |
description | text (multi-line) | Description. | |
acceptanceCriteria | text (multi-line) | Acceptance criteria. | |
storyPoints | enum | Valid ids: 0 (0), 0.5 (0.5), 1 (1), 2 (2), 3 (3), 5 (5), 8 (8), 13 (13), 21 (21), 34 (34), 55 (55), 89 (89). | |
businessValue | number | Business Value. | |
tags | tags | Tags. |
Planning & Assignment
| Field | Type | Required | Notes |
|---|---|---|---|
ownerId | reference → user | Requested by. Read only. | |
project | reference → PJ | Project. | |
epic | reference → EPIC | Epic. | |
sprint | reference → SPRINT | Sprint. | |
assigned | array of references → user | Assigned To. | |
duedate | date | Due Date. | |
startDate | date | Start Date. | |
completedDate | date | Completed Date. | |
subtaskCount | number | Number of Subtasks. Read only. |
Technical Details
| Field | Type | Required | Notes |
|---|---|---|---|
technicalNotes | text (multi-line) | Technical Notes. | |
testingNotes | text (multi-line) | Testing Notes. | |
deploymentNotes | text (multi-line) | Deployment Notes. |
Links & References
| Field | Type | Required | Notes |
|---|---|---|---|
pullRequestUrl | text (URL) | Pull Request. URL string. | |
issueUrl | text (URL) | Issue/Ticket URL. URL string. | |
designUrl | text (URL) | Design Documents. URL string. | |
documentationUrl | text (URL) | Documentation. URL string. |
Definition of Done
| Field | Type | Required | Notes |
|---|---|---|---|
definitionOfDone | array | Checklist. |
Attachments and additional panels
- Activity timeline panel attached.
- File attachment on
attachments. Allowed types: *.
Relationships
- Lookups:
projectpoints at aPJrecord;epicpoints at aEPICrecord;sprintpoints at aSPRINTrecord. - Related lists:
SUBTASKAvia comboKey (format:SUB|KBN|USA|ENT).
Creating a User Story via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "USA",
"level": 510,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"status": "Example status",
"priority": "1"
}Listing User Stories
GET /v1/entities/USA/SUB