Tasks: method overview
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Tasks in Bitrix24 are a unified workspace that helps organize team workflows: assigning small assignments and managing large projects. With tasks, you can track employee progress, monitor deadlines, and distribute responsibilities.
Quick links: all methods and events
User documentation: Bitrix24 tasks
Task method features
When using task methods, you must follow the parameter order specified in the parameter tables. Otherwise, the request will execute with errors.
Task card
A task card can be divided into blocks:
- description
- system and user fields
- task chat
- history and time tracking
The task description contains information about what needs to be done. You can add checklists, files, and links to other tasks to the text.
Checklists help create a list of steps to complete a task. You can manage checklists using the task.checklistitem.* method group.
If you need to avoid filling in the same fields manually for recurring tasks, use task templates. A template allows you to pre-save the title, description, participants, deadlines, project, checklist, and other parameters of a future task.
Create a link to tasks using the task.dependence.add method. Delete them using the task.dependence.delete method.
When creating a task, fill in the system fields: specify the responsible person, observers, deadline, tags, and so on.
If system fields are not enough, you can create your own user fields. They allow you to store information in various data formats: string, number, date with time, and yes/no. You can create, change, retrieve, or delete task user fields using the task.item.userfield.* method group.
In the new task card, discussions take place in the task chat. Since module version tasks 25.700.0, comments have been moved to the chat, so use task chat and messenger methods to work with messages. See details in the article New task card: overview of changes.
The result of working on a task can be written in a comment and recorded as a result. Manage task results using the tasks.task.result.* method group.
Time tracking in tasks monitors the time spent by an employee on a task. You can work with time tracking records using the task.elapseditem.* method group.
All actions with a task are recorded and retained in the task history. To retrieve the history, use the tasks.task.history.list method.
User documentation
Connection with Other Objects
Parent task. A task can have subtasks. In this case, it is considered a parent task. You can add a link to a parent task in the PARENT_ID parameter. You can retrieve a task identifier using the task creation method or the task list retrieval method.
Group or project. A task is linked by the group identifier GROUP_ID. You can retrieve the identifier using the new group creation method or the group list retrieval method.User. A task is linked to users via numeric identifiers in the following fields:
CREATED_BY— CreatorRESPONSIBLE_ID— Responsible personACCOMPLICES— Co-executorsAUDITORS— ObserversCHANGED_BY— Last user who changed the taskSTATUS_CHANGED_BY— Last user who changed the task statusCLOSED_BY— User who completed the task
You can retrieve a user identifier using the user.get method.
CRM. You can link CRM objects to a task: contacts, companies, leads, deals, invoices, and SPAs. To link an object, specify its identifier with a prefix in the UF_CRM_TASK parameter. For example, C_3 for contact with id = 3. You can retrieve the identifier using the create new CRM item method or the retrieve item list method.
Webmail. A task can be linked to an email by identifier via the UF_MAIL_MESSAGE parameter.
User documentation
Drive files
You can attach Drive files to a task description. In the UF_TASK_WEBDAV_FILES parameter, pass an array of Drive file IDs. Before each ID, specify the prefix n, for example: "UF_TASK_WEBDAV_FILES": ["n428", "n345"]. You can retrieve file identifiers in two ways.
Use one of the file upload methods:
Use one of the file list retrieval methods:
Attach files to a task using the tasks.task.files.attach method if the task has already been created.
Typical use-cases and scenarios
Flows
Flows are a tool that automates task distribution and execution. Employees do not need to search for who will perform a task. They place tasks into a department flow, and it automatically assigns an executor.
Flows can be managed using the tasks.flow.Flow.* group of methods.
User documentation
Scrum tasks
Scrum tasks are standard Bitrix24 tasks with extended capabilities for working with the Scrum methodology. In Scrum, a team can:
- estimate task complexity using story points
- attach tasks to epics
- place tasks in backlogs and sprints
- move tasks through sprint stages during the work process
For more details about Scrum and its methods, see the article Scrum: methods overview.
User documentation
Task operating modes
Kanban is a tool that helps visually represent task work in the form of columns and cards. Columns are work stages, and cards are tasks. Kanban is used for working with tasks in groups and projects.
"My plan" is a mode for managing your own tasks in a Kanban view. Each employee will have their own "My plan" stages.
Kanban and "My plan" stages can be managed using the task.stages.* group of methods.
Tasks in "Daily plan"
"Daily plan" is a list of to-dos, tasks, and meetings that you have scheduled for the workday. The task.planner.getlist method retrieves the list of tasks from the "Daily plan".
Widgets
An application can be embedded into a task card. Embedding allows you to use the application without leaving the card.
- Tab in the task card
TASK_VIEW_TAB - Right panel of the task card
TASK_VIEW_SIDEBAR - Link in the top part of the task card
TASK_VIEW_TOP_PANEL
An application can also be embedded in the task list:
- List context menu item
TASK_LIST_CONTEXT_MENU
In Kanban or "My Plan" task modes, there are two additional special embedding locations:
- Main dropdown menu item
TASK_USER_LIST_TOOLBAR,TASK_GROUP_LIST_TOOLBAR - Main dropdown menu item near robot settings
TASK_ROBOT_DESIGNER_TOOLBAR
Overview of Methods and Events
Scope:
taskWho can execute the method: depends on the method
Basic
|
Method |
Description |
|
Creates a task |
|
|
Updates a task |
|
|
Gets information about a task by |
|
|
Gets a list of tasks |
|
|
Attaches files to a task |
|
|
Delegates tasks |
|
|
Gets user counters |
|
|
Moves a task to "in progress" status |
|
|
Stops task execution and moves it to "waiting" status |
|
|
Moves a task to "deferred" status |
|
|
Moves a task to "completed" status |
|
|
Renews a task after its completion |
|
|
Approves a task |
|
|
Rejects a task |
|
|
Deletes a task |
|
|
Allows watching a task |
|
|
Stops watching a task |
|
|
Adds tasks to favorites |
|
|
Removes tasks from favorites |
|
|
Pins a task in the list |
|
|
Unpins a task in the list |
|
|
Gets available fields |
|
|
Checks access to the task |
|
|
Gets the task history |
|
|
Enables "Mute" mode |
|
|
Disables "Mute" mode |
|
|
Creates a dependency of one task on another |
|
|
Deletes a dependency of one task on another |
|
Event |
Triggered |
|
On task addition |
|
|
On task update |
|
|
On task deletion |
Task result
|
Method |
Description |
|
Adds a comment to the result |
|
|
Gets a list of task results |
|
|
Removes a comment from the task result |
Checklists
|
Method |
Description |
|
Adds a new checklist item to the task |
|
|
Updates checklist item data |
|
|
Gets a checklist item by its |
|
|
Gets a list of checklist items in the task |
|
|
Places a checklist item in the list after the specified one |
|
|
Marks a checklist item as completed |
|
|
Marks a completed checklist item as active again |
|
|
Deletes a checklist item |
|
|
Checks if an action is allowed for a checklist item |
|
|
Gets a list of methods and their descriptions |
Comments
Warning
Comment methods are not applicable to the new task card. Task discussions are held in the task chat. For details, see the article New task card: overview of changes.
|
Method |
Description |
|
Creates a new comment for a task |
|
|
Updates comment data |
|
|
Gets a comment for a task |
|
|
Gets a list of comments for a task |
|
|
Deletes a comment |
Time spent
|
Method |
Description |
|
Adds time spent to a task |
|
|
Updates parameters of a time spent record |
|
|
Gets a time spent record by its identifier |
|
|
Gets a list of time spent records for a task |
|
|
Deletes a time spent record |
|
|
Checks if an action is allowed |
|
|
Gets a list of methods and their descriptions |
Custom fields
|
Method |
Description |
|
Creates a new field |
|
|
Updates field parameters |
|
|
Gets a field by identifier |
|
|
Gets a list of fields |
|
|
Deletes a field |
|
|
Gets all available data types |
|
|
Gets all available custom field types |
Kanban and "My Plan" stages
|
Method |
Description |
|
Adds Kanban or "My Plan" stages |
|
|
Updates Kanban or "My Plan" stages |
|
|
Gets Kanban or "My Plan" stages |
|
|
Determines if the current user can move tasks in the specified object |
|
|
Moves tasks from one stage to another |
|
|
Deletes Kanban or "My Plan" stages |
Tasks in "Plan for the day"
|
Method |
Description |
|
Gets a list of tasks from "Plan for the Day" |
Flows
|
Method |
Description |
|
Create a stream |
|
|
Get a stream |
|
|
Change a stream |
|
|
Delete a stream |
|
|
Check if a stream with such a name exists |
|
|
Enable or disable a stream |