Alvaro Cuesta
When a comment is created through the Favro API, Favro automatically inserts a comment-thread anchor into the card body:
“User started a comment thread via API on date”
This is related to the behavior already reported in:
https://favro.canny.io/feature-requests/p/post-comment-via-api-without-adding-anchorsmention-to-card-body
Deleting this generated anchor produces an inconsistent state. The comment remains available when the card is opened, but the Kanban card no longer displays the comment icon or comment count. As a result, users looking at the board cannot tell that the card contains comments.
Comments created manually do not appear to have this problem.
Steps to reproduce
  1. Create or open a card in a Kanban board.
  2. Add a comment to the card using the Favro API.
  3. Open the card.
  4. Verify that Favro added an anchor to the card body similar to:
“User started a comment thread via API on date”
  1. Return to the Kanban view and verify that the card displays the comment icon and count.
  2. Open the card again.
  3. Delete only the automatically generated anchor using its trash icon, as shown in Image 1.
  4. Confirm that the API-created comment is still available inside the card.
  5. Return to the Kanban view, or reload the board.
Actual result
  • The API-created comment still exists and can be read when the card is opened.
  • The comment icon and count disappear from the card in the Kanban view.
  • From the board, the card appears to have no comments, as shown in Image 2.
  • This differs from comments written manually, whose indicator is displayed normally, as shown in Image 3.
Expected result
Deleting the generated anchor from the card body should not affect the Kanban comment indicator or count.
The comment count should be calculated from the comments that actually exist on the card, independently of whether an automatically generated anchor remains in the card body.
Alternatively, if deleting the anchor is intended to delete or detach the comment thread, Favro should:
  • Clearly warn the user before deletion.
  • Remove the associated comments consistently.
  • Avoid leaving comments accessible inside the card while hiding their existence in the Kanban view.
Impact
This creates inconsistent and misleading information between the card detail view and the Kanban view.
Users may:
  • Assume that a card has no comments.
  • Miss important updates or automated notifications.
  • Duplicate work because existing discussions are not visible from the board.
  • Overlook API-generated comments during reviews or daily board usage.
  • Avoid deleting the redundant API-generated anchor because doing so breaks comment visibility.
This is especially relevant for integrations that automatically create comments from GitHub, CI/CD systems, monitoring tools, or other external services.
Control test
For comparison:
  1. Add a comment manually through the Favro interface.
  2. Return to the Kanban view.
  3. The card correctly displays its comment icon and count, as shown in Image 3.
This suggests that the Kanban indicator for API-created comments may depend on the generated card-body anchor rather than on the comments stored on the card.
Reproducibility
Observed consistently with the described API-created comment. Favro should verify whether this affects:
  • All comments created through the API.
  • Only comments that create a new thread.
  • Existing cards created before and after recent updates.
  • Multiple comments within the same API-created thread.
  • Desktop, web and mobile clients.
  • Comment indicators after refreshing, reopening the board or clearing the client cache.
Attachments
  • Image 1: Automatically generated API comment-thread anchor and its delete button.
  • Image 2: Kanban card after deleting the anchor; no comment icon or count is displayed.
  • Image 3: Kanban card with manually created comments; the comment icon and count are displayed correctly.

Photo Viewer

View photos in a modal