Skip to content

Feat/task comments and im - #259

Closed
mnmyasis wants to merge 2 commits into
bitrix24:mainfrom
mnmyasis:feat/task-comments-and-im
Closed

mnmyasis wants to merge 2 commits into
bitrix24:mainfrom
mnmyasis:feat/task-comments-and-im

Conversation

@mnmyasis

@mnmyasis mnmyasis commented Sep 2, 2026

Copy link
Copy Markdown

Summary

Type of change

  • feat
  • fix
  • docs
  • chore
  • test
  • refactor
  • ci

Linked issue

Checklist

  • PR title follows Conventional Commits
  • pnpm lint passes
  • pnpm typecheck passes
  • pnpm test passes
  • New or changed code has tests
  • Public-facing changes reflected in docs/ and skills/ (if you change the tool-authoring conventions or checklist — not just add a tool — keep the human guide docs/ADDING-TOOLS.md and the agent skill skills/manage-bx24-template-mcp/adding-tools.md in sync)
  • No unrelated changes
  • No secrets in code, tests, or CI logs

Screenshots / logs

Notes for reviewers

Read counterpart to b24_task_comment_add (task.commentitem.getlist, v2).
Lets an agent catch up on a task's comment thread or check whether the
operator was @-mentioned (Bitrix24 renders mentions as [USER=<id>]Name[/USER]
inside the comment text, so callers match on that pattern).
…b24_im_message_list)

Bitrix24 portals on the newer Task Card UI move task discussion into a
linked chat — task.commentitem.* (b24_task_comment_list) returns empty
even when the task has an active thread. b24_task_get exposes the task's
chatId so an agent can bridge into the new im.* messenger domain:

- b24_task_get (tasks.task.get, v3) — verified against a live portal that
  this method's wire param is `id` (not `taskId`), the response root is
  `item` (not `task`), and responsible/chat only come back nested
  (`responsible.id` / `chat.id`) — `createdDate`/`createdBy` aren't valid
  TaskDto fields at all on this portal version.
- b24_im_dialog_list (im.recent.list) — recent Messenger dialogs (personal
  DMs, group chats, task chats) with unread state. im.recent.list was
  picked over the older im.recent.get after confirming on a live portal
  that im.recent.get silently ignores LIMIT.
- b24_im_message_list (im.dialog.messages.get) — read a dialog's messages,
  resolving authorId to authorName from the response's embedded user list.

Also documents on b24_task_comment_list that an empty result on these
portals likely means the discussion moved to the linked chat.
@mnmyasis mnmyasis closed this Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant