Monorail Project: gerrit Issues People Development process History Sign in
New issue
Advanced search Search tips
Starred by 1 user
Status: Released
Owner: ----
Closed: Jun 2016
Cc:



Sign in to add a comment
Deleting a draft inline comment causes the change's "Updated" field to be bumped
Project Member Reported by david.pu...@gmail.com, May 30 2016 Back to list
*****************************************************************
*****                                                       *****
***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!!  *****
*****                                                       *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, CYANOGENMOD,  *****
***** INTERNAL ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.*****
*****                                                       *****
*****   THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS     *****
*****                                                       *****
*****************************************************************

Affected Version: 2.12.2-2512-g0b1bccd

What steps will reproduce the problem?
1. From the change list, open a change that has not been updated for some time (in my test I chose one from 3 days ago)
2. On any file in the change, add an inline comment and save it
3. Go back to the change screen, check the "Updated" field
4. Go back to the change list, check the position of the change in the list
5. Go back to the change, open the file with the draft inline comment, and delete the draft comment
6. Go back to the change screen, check the "Updated" field
7. Go back to the change list, check the position of the change in the list


What is the expected output? What do you see instead?

At step 3 and 4, the "Updated" field is unchanged and the file remains in its position in the list (taking into account updates to other changes that may have been updated in the meantime).

However at steps 6 and 7, the "Updated" field is changed to "X seconds ago" (where X depends how long it takes you to get back to the change screen) and the change is now at the top of the list (or near the top, if other changes are also updated at the same time).

Looking at the change as an outside observer not aware of the actions taken with draft comments, one cannot see what has caused it to jump to the top of the list.

Please provide any additional information below.

 
Status: ChangeUnderReview
https://gerrit-review.googlesource.com/78151
Labels: FixedIn-2.13
Status: Submitted
Project Member Comment 3 by huga...@gmail.com, Sep 22 2016
Status: Released
Sign in to add a comment