STASK: Subtask
A subtask under a US user story with effort tracking, predecessor dependencies, and contractual deliverables.
STASK 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 STASK.Entity properties
| Property | Value |
|---|---|
| Entity code | STASK |
| Display name | Subtask |
| Plural | Subtasks |
| Level | 530 |
Use cases
A subtask under a US user story with effort tracking, predecessor dependencies, and contractual deliverables.
STASK is the subtask entity for the US (User Story) board variant, linked via comboKey SUB|US. It differs from SUBTASK and SUBTASKA by including: combo2 definitions for secondary indexing by user and status (enabling filtered views), a predecessor panel for task sequencing within a story, and a contractual deliverables panel (SDEL entity) for linking subtasks to supplier milestones. The name field is readonly because subtask names are typically set when created from the parent story. The task types (development, testing, documentation, design, research, deployment, review) classify work for team capacity planning. Effort tracking includes estimated hours, actual hours, workload percentage (in 5% increments), and auto-calculated remaining hours. The board is preloaded for team context. Calendar viewOption enables resource scheduling views alongside the standard grid. The Technical panel includes git branch, PR, code review, and test result links plus a completion checklist.
Fields
Task Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Task Name. Read only. |
status | enum | Yes | Valid ids: 0 (New), 1 (In Progress), 2 (Done), 3 (Blocked), 4 (Cancelled). |
user | reference → user | Yes | Assigned To. |
date1 | date | Start Date. | |
actualStartDate | datetime | Actual Start. Read only. | |
taskType | enum | Valid ids: development (Development), testing (Testing), documentation (Documentation), design (Design), research (Research), deployment (Deployment), review (Review). | |
date2 | date | Due Date. | |
actualEndDate | datetime | Actual End. Read only. | |
complexity | enum | Valid ids: trivial (Trivial), simple (Simple), medium (Medium), complex (Complex), verycomplex (Very Complex). | |
workload | number | Workload (%). | |
progress | number | Progress (%). | |
description | text (multi-line) | Description. | |
acceptanceCriteria | text (multi-line) | Acceptance Criteria. |
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. |
Deliverables & Stakeholders
| Field | Type | Required | Notes |
|---|---|---|---|
communicationPlan | text (multi-line) | Communication Plan. | |
escalationPath | reference → PPL | Escalation Path. |
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
- Activity log panel attached.
- Comments panel attached.
- File attachment on
attachments. Allowed types: *. - Additional panels:
predecessor,timelog.
Relationships
- Lookups:
escalationPathpoints at aPPLrecord. - Related lists:
STASKvia multiselect;STASKvia comboKey (format:SUB|US|STASK);SDELvia link.
Creating a Subtask via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "STASK",
"level": 530,
"comboKey": "SUB:<your-sub-id>|ENT:",
"status": 0,
"user": ""
} Listing Subtasks records
GET /v1/entities/STASK/SUB