Deleting a thread in a merge request results in a "Made a private contribution" activity note

Summary

Deleting a thread in a merge request and an issue results in a "Made a private contribution" activity note. Deleting a comment does not trigger any activity notes.

When a thread is exists in a merge request it appears like this in the activity feed:

CleanShot_2026-01-28_at_12.45.38

When the thread author deletes that thread, then that thread becomes

CleanShot_2026-01-28_at_12.49.20

This is a comment that suggested that this might affect issues too gitlab-foss#53742 (comment 188878577). (@mle confirmed this is true for threads in issues 2026-02-03).

Steps to reproduce

  1. Enable "Include private contributions on your profile" in "https://gitlab.com/-/user_settings/profile"
  2. Go to merge request
  3. Add a thread either by a review or start thread dropdown button
  4. After thread added to the merge request, delete that thread
  5. Look at your activity feed and that deleted thread appears as "Made a private contribution"

What is the current bug behavior?

Deleted thread appears as "Made a private contribution"

What is the expected correct behavior?

No activity should be presented since we don't display anything for deleting comments.

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited Feb 12, 2026 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading