A task’s comments and its Microsoft Teams thread are two ends of the same conversation. Comments you write in AB always post to the thread; a reply in the thread comes back to the task when it @mentions AB Projects. And a comment by itself notifies no one — mentions only happen when you pick people in the mention picker.
Mentions are opt-in, per comment. Below the comment editor sits the Mention in Teams notification picker — a row of member chips. Only the members you select are @mentioned in the Teams channel post and get Teams’ native notification. No chips selected means no pings.
Write a comment and mention people
- Open the task and go to its Comments section.
- Write the comment in the rich-text editor — formatting and image upload are supported.
- Pick who to notify. In the Mention in Teams notification row, click a member’s chip to select them; click again to deselect. Only members with a Teams identity in this project appear (someone who can’t be @mentioned in Teams isn’t listed).
- Post. The comment is saved on the task and posted to the linked channel, with your selected members @mentioned in the Teams message.
How the sync works
- Every comment posts to the linked channel, not just the first one. The first comment on a task starts a thread with an Adaptive Card (an interactive message card in Teams) showing the task details; each later comment is a reply in that same thread. See Adaptive Cards and Task Previews.
- Thread replies sync back when they @mention the bot. Reply in the task’s thread and include @AB Projects in the message — that reply is added to the task as a comment. This is a Microsoft Teams platform rule: a bot only receives channel messages that @mention it, so a plain reply without the mention stays in Teams only.
- Unregistered repliers are still captured. If the replier isn’t an AB Projects user yet, the comment is saved with a “(Teams)” label on their name, and the bot invites them to register so future comments link to their profile.
- Viewer replies stay in the channel. Replies from members with the read-only Viewer role are not copied into the task’s comment history — they can chat in the channel, but the audited task record only takes comments from members who can edit. See Role-Based Access Control.
Replied in the thread but it’s not on the task? The reply almost certainly didn’t @mention AB Projects. Reply again with the mention (type
@AB Projects and pick the app), or add the comment on the task itself — task-side comments always reach both places. We plan to lift this limitation in a future release.Comments not appearing in Teams at all? A project owner may have switched off New comments channel posts for the project — see the notification settings in Notifications and Reminders.
Quick reference
| Where you write | Where it ends up | Who gets notified |
|---|---|---|
| Task comment, chips selected | Task and the Teams thread | Selected members, via a real Teams @mention |
| Task comment, no chips | Task and the Teams thread | No one directly (the post is still visible in the channel) |
| Thread reply with @AB Projects | The thread and the task’s comments | Whoever Teams itself notifies for thread replies |
| Thread reply without the mention | The thread only — not recorded on the task | Whoever Teams itself notifies |
Best practices
- Mention only the people who need to act or weigh in — each chip is a real Teams notification.
- Keep discussion on the task (or @AB Projects-mentioned thread replies) instead of plain channel chatter, so nothing detaches from the work record.
- Glance at your selected chips before posting; it’s the difference between a useful ping and noise.
Comment where it’s convenient — the task and its Teams thread stay one conversation, and only the people you choose get pinged.