SUBTASK: Subtask
A subtask linked to a user story with effort tracking, blocking dependencies, and a development checklist.
SUBTASK 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 SUBTASK.Entity properties
| Property | Value |
|---|---|
| Entity code | SUBTASK |
| Display name | Subtask |
| Plural | Subtasks |
| Level | 530 |
Use cases
A subtask linked to a user story with effort tracking, blocking dependencies, and a development checklist.
SUBTASK is a subtask variant that links to US user stories via comboKey SUB|US|SUBTASK with story filter. Unlike STASK, it does not have combo2 secondary indexes, board preloading, or the contractual deliverables (SDEL) panel, making it a simpler subtask model. The description field is required (unlike SUBTASKA where it is optional), enforcing documentation of work items. Dependencies use a multiselect blockedBy property for tracking blocking relationships between SUBTASK entities, and related subtasks are shown via comboKey with story filter to scope visibility to the same user story. The entity includes full development lifecycle support: technical notes, testing approach, git branch/PR/code review/test result links, and a completion checklist (checkboxGroup). Time logging via TIMELOG entities (comboKey SUB|SUBTASK|TIMELOG) and a comments panel (CMT entity) provide activity tracking. Grid and calendar viewOptions support different planning perspectives.
Fields
Task Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Task Name. |
description | text (multi-line) | Yes | Description. |
acceptanceCriteria | text (multi-line) | Acceptance Criteria. | |
taskType | enum | Yes | Valid ids: development (Development), testing (Testing), documentation (Documentation), design (Design), research (Research), deployment (Deployment), review (Review). |
complexity | enum | Valid ids: trivial (Trivial), simple (Simple), medium (Medium), complex (Complex), verycomplex (Very Complex). |
Assignment & Scheduling
| Field | Type | Required | Notes |
|---|---|---|---|
status | enum | Yes | Valid ids: 0 (New), 1 (In Progress), 2 (Done), 3 (Blocked), 4 (Cancelled). |
story | reference → US | User Story. Read only. | |
user | reference → user | Yes | Assigned To. |
date1 | date | Start Date. | |
date2 | date | Due Date. | |
actualStartDate | datetime | Actual Start. Read only. | |
actualEndDate | datetime | Actual End. Read only. |
Effort Tracking
| Field | Type | Required | Notes |
|---|---|---|---|
hours | number | Estimated Hours. | |
actualHours | number | Actual Hours. | |
workload | enum | Valid ids: 0 (0%), 5 (5%), 10 (10%), 15 (15%), 20 (20%), 25 (25%), 30 (30%), 35 (35%), 40 (40%), 45 (45%), 50 (50%), 55 (55%), 60 (60%), 65 (65%), 70 (70%), 75 (75%), 80 (80%), 85 (85%), 90 (90%), 95 (95%), 100 (100%). | |
remainingHours | number | Remaining Hours. Read only. |
Implementation Details
| Field | Type | Required | Notes |
|---|---|---|---|
technicalNotes | text (multi-line) | Technical Notes. | |
testingApproach | text (multi-line) | Testing Approach. |
Links
| Field | Type | Required | Notes |
|---|---|---|---|
branchName | text | Git Branch. | |
pullRequestUrl | text (URL) | Pull Request. URL string. | |
codeReviewUrl | text (URL) | Code Review. URL string. | |
testResultsUrl | text (URL) | Test Results. URL string. |
Checklist
| Field | Type | Required | Notes |
|---|---|---|---|
checklist | array | Completion Checklist. |
Attachments and additional panels
- Comments panel attached.
- File attachment on
attachments. Allowed types: *. - Additional panels:
timelog.
Relationships
- Lookups:
storypoints at aUSrecord. - Related lists:
SUBTASKvia multiselect;SUBTASKvia comboKey (format:SUB|US|SUBTASK).
Creating a Subtask via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SUBTASK",
"level": 530,
"comboKey": "SUB:<your-sub-id>|US:<parent-id>|ENT:",
"name": "Example name",
"description": "Example text",
"taskType": "development",
"status": "0"
}Listing Subtasks
# All subtasks in your tenant
GET /v1/entities/SUBTASK/SUB
# All subtasks under a specific US parent
GET /v1/entities/SUBTASK/SUB:<your-sub-id>|US:<parent-id>