| Issue 2689: | demote a published change back to draft | |
| 1 person starred this issue and may be notified of changes. | Back to list |
There should be an option to demote a published change back to draft state. Typical scenarios that make this a useful feature are: * Change is work in progress, but may have inadvertently forgot to upload a change as a draft * Change was a draft, but again a new patchset was incorrectly uploaded as non-draft * Change turns out to be more complicated, typically only realised after one or more Verification failures During the process of demoting a change, it would probably make sense to query whether the reviewers list should be emptied. Again, intelligently so would be preferred, like presenting a cleaned out reviewers list preferably keeping non-interactive users kept ticked as reviewers (ie. suggest get rid of all human reviewers but keep CI reviewers such as Jenkins).
May 29, 2014
Project Member
#1
david.pu...@sonymobile.com
May 31, 2014
You may be interested in WIP plugin [1], that does something very similar. Unfortuntaly due to controversal discussion concerning new WIP value in Change.State enum, this feature (currently) cannot co-exist with DRAFT workflow. So for this plugin to work, Gerrit's core DRAFT Workflow has to be deactivited. This enables WIP plugin to abuse DRAFT enum value Change.State and implement different Rework Workflow Strategy on top of it: * promote/demote WIP/READY changes multipe times * show/hide the READY/WIP change from reviewers's dashboard [1] https://gerrit.googlesource.com/plugins/wip
Status:
AwaitingInformation
Apr 28, 2015
Setting a change back to DRAFT status can also be done by the force-draft plugin: https://gerrit-review.googlesource.com/Documentation/config-plugins.html#force-draft
Status:
Released
|
|
| ► Sign in to add a comment |