| Issue 2308: | Related changes not shown for merged changes | |
| 3 people starred this issue and may be notified of changes. | Back to list |
************************************************************ ***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL ***** ***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC. ***** ***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS! ***** ************************************************************ Affected Version: master What steps will reproduce the problem? 1. Review a change that is at the bottom of a stack of related open changes 2. Submit the change 3. What is the expected output? What do you see instead? Expect that the stack of related changes is still shown, so I can easily click to the next one in the series. Instead, the list is no longer displayed. I have to click back to the open changes list, or my dashboard, find the next change in the series, and open it from there. Please provide any additional information below.
Dec 5, 2013
Project Member
#1
edwin.ke...@gmail.com
Dec 5, 2013
It could be. In the case I described the dependency change is merged, but no new patch set is created on it, so the dependency should be the same. However I can see cases where it would be the same as 2073, like if the merge strategy is cherry pick or rebase if necessary.
Dec 19, 2013
The new change UI no longer offers the "Depends On" and "Needed By" navigation links. Once a change is merged, in the new UI there is no way to navigate to the change's related commits, since "related changes" are not populated for merged changes.
Jul 18, 2014
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |