Gerrit 3.10.1+ UI Reported Bug Details.

[mail...@gmail.com]

Hi,

We recently upgraded our Gerrit staging environment from version 3.9.6 to 3.11.7. After the successful upgrade, we noticed that a UI bug (https://issues.gerritcodereview.com/issues/383975884) remains unresolved, which was originally introduced in version 3.10.1.

Could you please confirm whether this bug is being addressed and provide any tentative timelines for a fix? This information will help us decide whether to proceed with or postpone the upgrade.

Thannks, Srini

[Dhruv Srivastava]

From the bug

> post a reply to that comment using https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#comment-input populating `in_reply_to` with the id of the original comment, but don't populate the `line` nor the `range`.

Why are you posting a reply without the field set? Can you create the comment while setting the field?

I don't think this is a UI bug, but rather a non-typical use of the REST API.

Given this I don't think it's very likely this bug will be prioritised, since it doesn't affect most of the users.

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/77af71f2-ed96-4c8c-bfae-b620c29c7275n%40googlegroups.com.

[Dhruv Srivastava]

OTOH, as AI tooling creates more comment replies using the API, we will run into this issue again.

The fix is fairly straightforward, so I created it here: https://gerrit-review.googlesource.com/c/gerrit/+/528381