Bug 1360173 - Cherry-picking changes to release branches via Gerrit Web UI wrongly sets the 'Topic' field
Summary: Cherry-picking changes to release branches via Gerrit Web UI wrongly sets the...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Nigel Babu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-26 07:23 UTC by Anoop C S
Modified: 2017-03-03 08:57 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-03 08:57:33 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Anoop C S 2016-07-26 07:23:50 UTC 
Description of problem:
When changes are being back ported via Gerrit Web UI to corresponding release branches, 'Topic' field of the newly created change is being appended by the name of the branch to which it is being cherry-picked.

Version of Gerrit:
v2.12.2 on https://review.gluster.org

How reproducible:
Always

Steps to Reproduce:
1. Select a particular change on master branch via https://review.gluster.org 
2. Click on `Cherry-Pick` button
3. Specify a release branch to which the change is to be cherry-picked
4. Click on `Cherry-pick Change`

Actual results:
Newly created change has 'Topic' set in the format: bug-<#bug-id>-<release-branch-name>

Expected results:
Newly created change must have the 'Topic' field set in the format: bug-<#bug-id>
Comment 1 Nigel Babu 2017-03-03 08:57:33 UTC 
I've gone looking for this. Turns out, this is an intentional change in Gerrit UI. See: https://gerrit-review.googlesource.com/#/c/66440/

Marking as WONTFIX.
Note You need to log in before you can comment on or make changes to this bug.