Elbuz keeps task discussions inside the organizer item: comments, @mentions, and a log of who changed what. Agreements don't get lost in messengers and take a minute to find.
When you need this:
- Ask the assignee about a task — all item participants get notified of the comment.
- A question for one person — an “@login” mention sends them a separate “mentioned you” notification.
- Someone moved the due date or status — “Change history” shows who and when.
- A manager wants to stay in the loop — item participants are notified of every comment, no mentions needed.
Where to start: open the item → “Comments” section → write a comment.
What comments and change history do
- Comments in the item — the discussion stays right under the task.
- @mentions — the person mentioned gets a separate, easy-to-spot notification.
- Notifications to all participants — as a toast and a row in the “Notifications” feed.
- Deleting your own comment — instead of editing.
- Change history — who changed the status, due date, priority or participants, and when.
Write a comment
Type your text in the “Write a comment… (Ctrl+Enter to send)” field. Send it with the “Send” button or Ctrl+Enter. Then Elbuz does the following:
- Checks that the item is open to you, meaning you are one of its assignees or participants. If not, the comment isn't saved and an “Update failed” toast appears.
- Rejects empty text. A comment made of spaces only isn't saved.
- Saves the comment with its author and time. The feed refreshes and the field is cleared.
- Sends notifications to the item participants — who gets what is described below.
Comments appear in the order they were added: oldest at the top, newest at the bottom. Everyone sees the comment time in their own time zone, so for colleagues in different zones it matches once you allow for the offset. The feed shows all of the item's comments in one list, with no limit and no “more” loading.
A counter appears next to the “Comments” section heading. While there are no comments yet, there is no counter either, and the section says “No comments yet. Start the discussion — all participants will see it.”
A comment is plain text. Line breaks are kept, and long text is fine. If you paste a piece of , it is shown as text, not as markup.
A sent comment can't be edited. Made a mistake? Delete your comment and write it again. Notifications that have already gone out are not recalled.
1
Comment counter2
Highlighted mention3
Comment field4
Hint about @- The counter next to the heading shows how many comments the record has.
- A mention in the comment text shows whom the author addressed.
- The comment field: Ctrl+Enter sends without the mouse.
- The hint under the field: typing @ opens the list of participants.
Mention a colleague with @
Use a mention when a comment is meant for a specific person and they need to spot it among the others. A hint is always shown under the field: “Type @ to mention a participant — they will be notified. Other participants also learn about new comments.”
How to do it:
- Type “@” in the field. A list of the item's active participants drops down under the field, with each person's name and login. You yourself and disabled employees aren't in the list. It shows no more than 8 people — if you don't see the one you need, keep typing the name.
- Keep typing — the list narrows by both name and login. For example, “@ol” leaves people whose name or login contains these letters.
- Use the ↑ and ↓ arrows to pick a person, then press Enter or Tab. You can also just click with the mouse. Esc closes the list without inserting anything.
@loginis inserted, followed by a space. The login, not the name: it's unique and has no spaces, so Elbuz knows exactly whom you mean. Keep the space after the login: a mention is “@” plus letters, digits, “_”, “.” and “-”, so a period right after the login (“@olena.”) breaks it.
Once the comment is sent, participant mentions are highlighted in the comment feed — you can see at a glance whom the author addressed.
1
Participant row2
Field with @- A participant row shows the name and the login; the login is what gets inserted into the text.
- Keep typing after @ to narrow the list.
Only item participants can be mentioned
The list after “@” contains only people added to the “Performer” field (task, project, table, form) or the “Member” field (note, document) in the “Advanced” section. If there are no participants besides you, instead of the list you see “Only participants of the item can be mentioned. Add them in the “Additional” section.”
You can type the @login of someone who isn't on the item by hand, but nothing happens: they get no notification, and the mention isn't highlighted. The item isn't open to them, and Elbuz doesn't send a link to a place the person can't get into anyway.
To bring in a new person, first add them as a participant, and only then mention them.
Only the item's author can change this list: for everyone else the field is read-only, and the server won't accept a change from them either. The author can't remove themselves from the participants — Elbuz keeps them on the list. How participants and assignees work in general is covered in the article about tasks and projects.
Who gets notified and where
As soon as a comment is saved, Elbuz goes through all the item's participants. Everyone except the author gets a notification. Only the text differs:
- people mentioned via
@login— “‹Author› mentioned you: ‹item name›”, with an orange marker; - other participants — “‹Author› commented: ‹item name›”, with a violet-blue marker;
- the comment author — nothing;
- anyone who isn't an item participant — nothing, even if their login is in the text;
- disabled employees — nothing.
The notification shows the first 160 characters of the comment. The rest is read in the item itself.
- Action or result
- Decision: the path depends on the answer
Where exactly it arrives
Only in the Elbuz interface. A toast pops up, and a row appears on the “Notifications” tab of the “Notifications and operations” panel. The panel opens from the badge on the taskbar at the bottom of the screen: a checklist icon with an unread counter next to it. The “Open” button in the row opens that same item.
If the person is offline right now, the notification isn't lost: it is saved and waits in the “Notifications” feed after sign-in. The “Open” button also works in such notifications loaded from history after a page reload. Any item participant can open the form this way, even without permission for that list's window.
After sign-in or a reload, the feed loads only the 30 latest entries — notifications and operations together. There is no “more” button: anything older no longer shows in the feed. Notifications loaded from history show only the time (HH:MM), without the date.
The notification is built in the recipient's language — the interface language set in their employee card. A colleague who works in English gets “commented” even if the comment author works in Russian.
Comment notifications are not sent by email or to Telegram. Anyone who doesn't open Elbuz won't learn about a comment until they sign in.
Notifications older than 90 days are deleted from the database during system cleanup. Cleanup runs together with import, export, price list processing and the parser, not on a schedule.
1
Mention notification2
Open button- A notification that you were mentioned via @.
- The Open button opens the same record.
Delete your comment
Each of your comments has “Delete” under it. Elbuz asks “Delete the comment?”, and once you confirm, the comment disappears from the feed.
- You can delete only your own comment. Nobody can delete someone else's — neither the item author nor the account owner.
- Notifications already sent stay in people's feeds. Deleting doesn't recall them.
- If the whole item is deleted, the notifications about its comments don't disappear either, but their “Open” button shows a “No access” window.
- There are no replies “to a comment”; the feed is flat, so deleting doesn't affect other comments.
Change history
The “Change history” section is collapsed. Each time you expand it, Elbuz loads fresh data, so an edit from a minute ago shows too. Newest rows on top, in write order; the form shows up to the last 100. Each row: what changed, date and time, who changed it. Everyone the item is open to sees the history.
What is recorded
Each save compares the item “before” and “after” and writes one row with only what actually changed, for example: “Status: New → Finished; Due date: 2026-09-27 10:00 → 2026-09-30 18:00”. Tracked fields:
- name, status, priority, category, project;
- due date — the “Deadline date, until” field;
- participants — by name;
- the “Archive”, “Trash”, “Favorite” and “Pinned to Top” checkboxes — in the history they appear as “Archived”, “In trash”, “Favorite”, “Pinned”;
- description — only the fact that it changed, as a “Description changed” row. The text itself isn't stored: a description can be large or encrypted.
Creating an item writes an “Item created” row.
An autosave that changed nothing writes no row. Tick just the “Favorite” checkbox, and exactly one row appears, not a dozen.
Where the rows come from
A row appears after:
- saving any of the six forms;
- an edit in the list table, ticking “done”, a bulk action on several items, or a quick add;
- moving a due date in the Calendar — by dragging the event or in the event form;
- dragging a card on a board into a column linked to a status, and changes made by board automations.
If an automation assigned someone responsible, that person is added to the item's participants, and a “Participants: …” row appears in the history. The same rows are visible in the general “Operation log” with the “Organizer: changes” type.
How long it is kept and from what date
The history lives as long as the item does. System cleanup removes rows older than 14 days from the general “Operation log”, but the “Organizer: changes” type is excluded from that cleanup. Delete an item, and its history is deleted with it.
History recording started on 26.09.2026. Changes made earlier weren't recorded anywhere and can't be restored.
In what language
In the form, the history is assembled in the viewer's language: field names, “Yes/No”, priorities. Status, category and project values are stored in the language of whoever made the change, and as they were named at that moment. In the general “Operation log”, the row text stays in the language of the person who made the edit.
1
Row with several changes2
Who and when3
Item created- One save is one row, even when several fields changed.
- Each row shows the date and the author of the change.
- Item created is the oldest row; new rows are added on top.
What the history doesn't include
- items of the “To-Do List” inside a task — ticks there aren't recorded;
- comments, files, links;
- reminder rule settings, except the due date itself;
- card moves between board columns as such — boards have their own history, see the article about boards; only a status change reaches the item history, if the column is linked to a status;
- who simply viewed the item.
Scenarios
A question for the assignee without a messenger
In the task you write: “@olena, the customer asks to move it to Friday?”. Olena gets “mentioned you”, clicks “Open” and replies in the same item. The agreement stays with the task, not on someone's phone. One condition: Olena must be an item participant.
Who moved the due date
Open the item, expand “Change history” and find the “Due date: … → …” row. Next to it you see the date, time and the user who did it. This works for changes made since 26.09.2026 — in the form or list, and in the Calendar.
A manager in the loop without mentions
Just add the manager to the item's participants. They will get “commented” on every comment, and there is no need to mention them each time.
After a vacation
Notifications that arrived while you were away wait on the “Notifications” tab of the “Notifications and operations” panel, but after sign-in the feed shows only the 30 latest entries, operations included. After a long absence, some of the older ones won't make it there.
So it's more reliable to go through your items and check their “Comments”. Mentions stand out in the feed with an orange marker.
What to do when a comment notification didn't arrive
| What you see | Why | What to do |
|---|---|---|
| A colleague says the mention notification didn't arrive | The person isn't an item participant or is disabled; they were mentioned by name or with a typo in the login; there is a period right after the login (“@olena.”); the login contains “@” (the login is an email address) | Ask the item author to add them as a participant, then mention them from the list after “@” and keep the space after the login. An email-address login won't work as a mention (who can be mentioned) |
| Comment notifications don't arrive by email or in Telegram | Comment notifications go only to Elbuz itself | Check the “Notifications” tab of the “Notifications and operations” panel (where it arrives) |
| “Only participants of the item can be mentioned. Add them in the “Additional” section.” | There are no participants on the item besides you | Add participants in “Advanced” — the item author can do this (participants) |
| There is no “Delete” under a comment | The comment is someone else's, and you can delete only your own | Ask the comment's author to delete it (deleting) |
| “No changes yet. Who changed the status, due date, participants and other fields — and when — will appear here.” | The item hasn't changed since 26.09.2026, and earlier changes weren't recorded | Nothing: a row will appear after the first change (from what date) |
| “Open” in a notification shows “No access” | The item the notification was about has been deleted, but the notification itself stayed in the feed | Nothing can be restored: the item was deleted together with its comments and history (how long it is kept) |
| “Update failed” after “Send” | The item isn't open to you — for example, you were removed from the assignees or participants | Ask the item author to add you back to the “Performer” or “Member” field (participants) |
| The presentation form has no “Comments” section | Presentations don't have comments | Comments are available in tasks, notes, projects, documents, tables and forms (where to find it) |
FAQ
Can I fix a comment I've already sent?
No. Comments can't be edited. Delete your comment and write it again. The notifications about the first version are already in people's feeds, and deleting doesn't recall them.
Why didn't my colleague get a notification even though I typed their @login?
Mentions work only for item participants. If the person isn't in the “Performer” or “Member” field under “Advanced”, there's no notification or highlight. Or there's a period right after the login, or “@” inside it — add a space after the login. Once the item author adds them, mention again.
Will I get comment notifications by email or in Telegram?
No. Comment notifications arrive only in Elbuz: as a toast and a row on the “Notifications” tab of the “Notifications and operations” panel. If the person is offline, they'll see it after signing in.
Can the task author delete someone else's comment?
No. Everyone deletes only their own comments. Neither the item author nor the account owner can delete someone else's comment.
Why doesn't the change history show what was changed last month?
History recording started on 26.09.2026. Changes made earlier weren't recorded anywhere. From that date on, rows are kept for as long as the item exists.
Does the change history show what exactly was written in the description?
No. Only the fact is recorded — a “Description changed” row. The description text can be large or encrypted, so it doesn't go into the history.
Does the history include a due date moved in the Calendar or a status changed on a board?
Yes. A due date moved in the Calendar, a card dragged into a status-linked column, and board automation changes go into the history like an edit in the form. Card moves between columns not linked to a status are kept in the board history.
How do I split a task into subtasks and a to-do checklist?
The organizer has no subtasks. Add small steps to the “Task To-Do List” card of the task form — each has a name, description, order and a “Complete status” checkbox. Make large parts separate tasks with the same “Project”: each gets its own assignee, due date and reminders.
Where to find it and who has access
Comments have no window of their own: they are a section inside the form of a task, note, project, document, table or form. Presentations don't have it.
- Menu
- Organizer → Tasks / Notes / Projects / Documents / Tables / Forms
- From the list
- “Edit” on a card or in a table row opens the item form
- From a notification
- the “Open” button in the “Notifications” feed takes you straight to the item
- In the form
- the “Comments” link in the navigation at the top; section order: “Comments” → “Change history” → “Link list”
- Access rights
- being on the item (assignee or participant); the window permission is only needed to open the list
- Prepare
- add colleagues as item participants: only they can be mentioned and notified
Related topics
- If you still need to add a colleague to the item's participants — tasks and projects.
- If a colleague should get a reminder on the due date rather than a comment — organizer reminders.
- If a card was dragged on a board and you need to know who did it — kanban boards.
- If you need to discuss a document, table or form — organizer documents.
