Skip to content
Leadtime
English
Esc
navigateopen⌘Jpreview

Get stack data for a user

What is the Stack? The Stack view shows a person’s personal weekly schedule and serves as their personal task overview. It acts like a personal Kanban board that helps specialists work through tasks in a focused, distraction-free way. The Stack automatically follows the order from pipeline planning, showing exactly which tasks are planned for the employee and in what priority order.

Task Filtering Logic: The stack includes tasks from two sources:

  1. Pipeline tasks: Tasks that are in the user’s pipeline for the current week (determined by the today parameter). These tasks appear regardless of whether they are assigned to the user or have the user as accountable. Pipeline tasks appear in the toDo and done columns.
  2. Non-pipeline tasks: Tasks filtered by the Assigned field (not the Accountable field). Only tasks where assignedToId equals the userId are included. These appear in giveFeedback, getFeedback, and backlog columns.

Important: Unlike the Pool view which filters by Accountable field, the Stack filters non-pipeline tasks by the Assigned field (assignedToId). Pipeline tasks are included regardless of assignment or accountability.

How to call this endpoint:

  • Both userId and today are required. Do not call GET /tasks/stack without them.
  • To show the current user’s own stack, first call GET /account/info and use its userId.
  • today must be an ISO date string such as 2026-07-08; use the current date unless the user asks for another week.
  • Example: GET /tasks/stack?userId=<current-user-id>&today=2026-07-08.
  • Empty columns are a valid successful result when the user has no stack tasks.

What data is returned: The response contains tasks organized into five columns that show how far tasks are in the workflow:

  • toDo: Tasks that need to be worked on this week. These are tasks from the pipeline (regardless of assignment) that are in “New” or “In Progress” status.
  • giveFeedback: Tasks where the expert should give feedback to others. These are tasks where the user is assigned (filtered by Assigned field, not Accountable) and are in “Feedback” status.
  • getFeedback: Tasks that are waiting for feedback from others. These are tasks where the user is NOT assigned (filtered by Assigned field) but are in “Feedback” status.
  • done: Finished tasks from the pipeline (regardless of assignment) that are in “Closed” or “Resolved” status.
  • backlog: Tasks that are assigned to the user (filtered by Assigned field) but are not part of this week’s pipeline. These could be planned for coming weeks.

Task sorting and prioritization:

  • Tasks are sorted by priority (High > Normal > Low) then by shortNumber (ascending)
  • Pipeline tasks are prioritized and appear first in their respective columns
  • The order matches the priority set during pipeline planning

Permission requirements: Access is controlled by Stack permissions:

  • Stack.canViewAll: Can view any user’s stack
  • Stack.canViewOwnTeams: Can view stacks of users in the same actual team membership. The role name alone is not enough; users must share a Team/UsersOnTeam relation.
  • Stack.canViewOwn: Can only view own stack

Task details included: Each task includes comprehensive information: ID, title, icon, short number, organization color and name, project details, status, summary, priority, type, deadline, estimated/spent time, comments count, assigned users, and tags. The spentTime field is only visible if the user has Tasks.seeLoggedTime permission.

Note: If you need to retrieve all tasks with custom filtering, sorting, or pagination capabilities, consider using the GET /tasks/grid endpoint instead. The grid endpoint provides more flexible filtering options and is better suited for retrieving large datasets or when you need to filter by multiple criteria simultaneously.

GET/tasks/stack
Authorization
AuthorizationOAuth2 access token · headerrequired
Scopes:api:read
or
AuthorizationBearer token (JWT) · headerrequired
Query parameters
userIdstringrequired
Required UUID of the user whose stack to retrieve. To retrieve the current user's own stack, call GET /account/info first and use its userId here. **Important**: The stack includes (1) pipeline tasks regardless of assignment, and (2) non-pipeline tasks filtered by the Assigned field (where assignedToId equals this userId). The user must exist, not be deleted, and belong to the same workspace as the authenticated user.
todaystringrequired
Required date in ISO 8601 format (YYYY-MM-DD) used for pipeline calculations. Use the current date for the current week unless the user asks for another week. This date determines which tasks are included in the current week pipeline and affects task sorting and column assignment.
Responses
200Stack data successfully retrieved. Returns tasks organized into five columns (toDo, giveFeedback, getFeedback, done, backlog). Pipeline tasks are included regardless of assignment. Non-pipeline tasks are filtered by the Assigned field (assignedToId). Includes comprehensive task details: IDs, titles, priorities, assignments, time tracking, and more.
columnsStackColumnDto[]required
Array of stack columns representing different workflow stages. Always includes all five column types (toDo, giveFeedback, getFeedback, done, backlog), even if some columns are empty. Columns appear in this order. **Task filtering**: Pipeline tasks (regardless of assignment) appear in toDo and done columns. Non-pipeline tasks filtered by Assigned field (assignedToId) appear in giveFeedback, getFeedback, and backlog columns. Tasks are sorted by priority and pipeline order.
Show properties
Array of StackColumnDto
tasksStackTaskDetailsDto[]required
Array of tasks in this column. Tasks are sorted by priority (descending) then shortNumber (ascending), with pipeline tasks appearing first.
Show properties
Array of StackTaskDetailsDto
accountableIdobject | nullrequired
UUID of the user who is accountable for the task (responsible person). Can be null if no one is assigned as accountable.
assignedToIdobject | nullrequired
UUID of the user who is assigned to work on the task (Assigned field). Can be null if no one is assigned. **Important**: Non-pipeline tasks in the stack are filtered by this field (assignedToId). Pipeline tasks appear regardless of this field. This field determines which column the task appears in for feedback-related columns (giveFeedback vs getFeedback).
colorstringrequired
Color code (hex format) representing the organization that owns the task. Used for visual identification.
commentsCountnumberrequired
Total number of comments on the task. Includes all comments from team members.
deadlineobject | nullrequired
Deadline date in ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss.sssZ). Can be null if no deadline is set.
estimatedTimeobject | nullrequired
Estimated time to complete the task, measured in hours. Can be null if no estimate is provided.
iconobject | nullrequired
Icon identifier for the task. Can be null if no icon is set.
idstringrequired
Unique identifier (UUID) of the task
orgNamestringrequired
Full name of the organization that owns the task. Provides human-readable context.
organizationShortNamestringrequired
Short name or abbreviation of the organization that owns the task
priorityobjectrequired
Priority level of the task. Used for sorting: High > Normal > Low. Tasks with higher priority appear first in their column.
Show properties
object
projectIdstringrequired
UUID of the project this task belongs to
projectShortNumberobject | nullrequired
Short number of the project this task belongs to. Can be null if task is not associated with a project.
shortNumbernumberrequired
Short number of the task within its workspace. Used for display and sorting purposes.
spentTimeobject | null
Total time already spent on the task, measured in hours. This field is only visible if the authenticated user has the Tasks.seeLoggedTime permission. Can be null if no time has been logged yet.
statusIdstringrequired
UUID of the task status. The status determines which column the task appears in (toDo, giveFeedback, getFeedback, done, backlog).
summaryobject | nullrequired
Optional summary or description of the task. Provides additional context about what needs to be done.
tagsstring[]required
Array of tag names associated with the task. Tags enable cross-project organization and filtering of tasks.
titlestringrequired
Title or name of the task
typeIdstringrequired
UUID of the task type. Task types define workflows, fields, and statuses available for the task.
typeobjectrequired
Type of column indicating the workflow stage. Possible values: toDo (pipeline tasks in New/InProgress status), giveFeedback (tasks assigned to user in Feedback status), getFeedback (tasks NOT assigned to user in Feedback status), done (pipeline tasks in Closed/Resolved status), backlog (non-pipeline tasks assigned to user). **Note**: Pipeline tasks appear regardless of assignment. Non-pipeline tasks are filtered by Assigned field.
Show properties
object
400Invalid request parameters. Occurs when userId is not a valid UUID format or today is not a valid ISO 8601 date format (YYYY-MM-DD).
messagestring
statusCodenumber
401Unauthorized - Invalid or missing authentication token
403Access denied. Occurs when the authenticated user does not have the required Stack permissions (Stack.canViewAll, Stack.canViewOwnTeams, or Stack.canViewOwn) to view the requested user's stack, or when permission validation fails (e.g., user with Stack.canViewOwnTeams trying to view stack of user from different team, or user with Stack.canViewOwn trying to view another user's stack).
messagestring
statusCodenumber
404User not found. Occurs when the userId does not exist, has been deleted (deletedAt is not null), or does not belong to the same workspace as the authenticated user.
messagestring
statusCodenumber
Request
curl -X GET "https://leadtime.app/api/public/tasks/stack?userId=aff55c87-49c6-4d5d-9b0b-bf7478e2d504&today=2025-11-04" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
Response
{
  "columns": [
    {
      "tasks": [
        {
          "accountableId": {},
          "assignedToId": {},
          "color": "string",
          "commentsCount": 0,
          "deadline": {},
          "estimatedTime": {},
          "icon": {},
          "id": "string",
          "orgName": "string",
          "organizationShortName": "string",
          "priority": {},
          "projectId": "string",
          "projectShortNumber": {},
          "shortNumber": 0,
          "spentTime": {},
          "statusId": "string",
          "summary": {},
          "tags": [
            "string"
          ],
          "title": "string",
          "typeId": "string"
        }
      ],
      "type": {}
    }
  ]
}