Issue 2710: ChangeScreen2: Cherry-picking a change doesn't trigger re-rendering of original change
Status:  Released
Owner: ----
Closed:  Jun 2014
Project Member Reported by David.Os...@gmail.com, Jun 11, 2014
Affected Version: master

What steps will reproduce the problem?
0. open new change screen
1. cherry-pick a change from branch foo to branch bar
2. new (target) change is opened
3. change to the original change
4. Message is missing:

"This patchset was cherry picked to branch bar as commit c5ad912e0" 

Work around: clear browser caches.

The problem seems to be that the oiginal change is not get updated and thus not re-rendred. 
Jun 11, 2014
Project Member #1 David.Os...@gmail.com
(No comment was entered for this change.)
Summary: ChangeScreen2: Cherry-picking a change doesn't trigger re-rendering of original change (was: New change screen: Cherry-picking a change doesn't trigger re-rendering of original change )
Jun 22, 2014
Project Member #2 David.Os...@gmail.com
(No comment was entered for this change.)
Status: Accepted
Jun 22, 2014
Project Member #3 David.Os...@gmail.com
https://gerrit-review.googlesource.com/58002
Status: ChangeUnderReview
Jun 23, 2014
Project Member #4 edwin.ke...@gmail.com
(No comment was entered for this change.)
Status: Submitted
Labels: FixedIn-2.9
Jul 18, 2014
Project Member #5 edwin.ke...@gmail.com
(No comment was entered for this change.)
Status: Released