SPRINTP: Sprint
The SPRINTP entity: A time-boxed iteration within a project, grouping backlog items for delivery.
Default definition. This article describes the default
SPRINTP 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 SPRINTP.Entity properties
| Property | Value |
|---|---|
| Entity code | SPRINTP |
| Display name | Sprint |
| Plural | Sprints |
| Level | 430 |
Use cases
SPRINTP is a project-level agile entity at level 430. The General panel uses a 30/70 split: left column captures sprint details (name, goal textarea, start/end dates, status as Planning/Active/Completed with default planning); right column has a full-height relatedlist of BACKLOGP items linked via comboKey2 format SUB|SPRINTP, with hideaddexisting set and click-through enabled. Fields shown in the backlog list: title, type, priority, status.
Fields
Sprint
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Sprint Name |
goal | text (multi-line) | Sprint Goal | |
startDate | date | Yes | Start Date |
endDate | date | Yes | End Date |
status | enum | Yes | Status Valid ids: planning (Planning), active (Active), completed (Completed). |
Relationships
- Related lists:
BACKLOGP(formatSUB|SPRINTP).
Creating a Sprint via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SPRINTP",
"level": 430,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"startDate": "2026-01-01",
"endDate": "2026-01-01",
"status": "planning"
} Listing Sprints records
GET /v1/entities/SPRINTP/SUB