Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1360173

Summary:	Cherry-picking changes to release branches via Gerrit Web UI wrongly sets the 'Topic' field
Product:	[Community] GlusterFS	Reporter:	Anoop C S <anoopcs>
Component:	project-infrastructure	Assignee:	Nigel Babu <nigelb>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, gluster-infra
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-03 08:57:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.