Issue 3131: Don't offer 'Fix' on comments on closed changes
Status:  Released
Owner: ----
Closed:  Jan 2015
Project Member Reported by edwin.ke...@gmail.com, Jan 28, 2015
Affected Version: master (aka 2.11)

What steps will reproduce the problem?
1. Go to a merged change
2. open a file, add an inline comment and publish it
3. go to the inline comment and see that 'Fix' is offered on it

What is the expected output? What do you see instead?
It's expected that 'Fix' is not offered since the change is merged and editing it makes no sense.

Please provide any additional information below.
Editing the merged change reveals several other issue:
1. click on 'Fix'
2. edit the file and save
3. go back to change screen

=> a change edit gets created, should it possible at all to create a change edit on a merged change? Should this be prevented by the REST endpoints on server side?
=> it's not possible to delete (or publish) the change edit (button is not shown)
=> The GetRelated endpoint fails with a NullPointerException and '500 Internal server error' is shown in the 'Related Changes' tab

Jan 28, 2015
Project Member #1 David.Os...@gmail.com
https://gerrit-review.googlesource.com/63817
Status: ChangeUnderReview
Jan 29, 2015
Project Member #2 david.pu...@sonymobile.com
(No comment was entered for this change.)
Status: Submitted
Labels: FixedIn-2.11
Apr 16, 2015
Project Member #3 david.pu...@sonymobile.com
(No comment was entered for this change.)
Status: Released