SUBTASKA: Subtask
A subtask variant for the USA user story board with effort tracking, dependencies, and time logging.
SUBTASKA 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 SUBTASKA.Entity properties
| Property | Value |
|---|---|
| Entity code | SUBTASKA |
| Display name | Subtask |
| Plural | Subtasks |
| Level | 530 |
Use cases
A subtask variant for the USA user story board with effort tracking, dependencies, and time logging.
SUBTASKA is the subtask entity paired with the USA (alternative user story) board variant. It is structurally identical to SUBTASK but exists as a separate entity to maintain data isolation between different board configurations. The description field is optional (required:false) unlike SUBTASK where it is required, reflecting a lighter-weight task capture model. Dependencies reference other SUBTASK entities (not SUBTASKA) for blocking relationships, which may indicate shared dependency tracking across board variants. Related subtasks are scoped via comboKey SUB|US|SUBTASK with story filter. Like SUBTASK, it includes time logging (TIMELOG via comboKey SUB|SUBTASK|TIMELOG), comments (CMT), file attachments, technical details with git/PR links, and a completion checklist. The separate entity code allows USA boards to have independent subtask lists, grid columns, and lifecycle management from US boards.
Fields
Task Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Task Name. |
description | text (multi-line) | 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": "SUBTASKA",
"level": 530,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"taskType": "development",
"status": "0",
"user": ""
} Listing Subtasks
GET /v1/entities/SUBTASKA/SUB