Bug 819709

Summary:	Groups dropped when moving bugs between products
Product:	[Community] Bugzilla	Reporter:	Simon Green <sgreen>
Component:	Creating/Changing Bugs	Assignee:	Simon Green <sgreen>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	high
Version:	3.6	CC:	ebaak, jfearn
Target Milestone:	4.2-4	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.2.2-4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-30 23:39:35 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 Simon Green 2012-05-08 03:12:17 UTC

Description of problem:
Mass moving bugs between products seems to drop all group privileges.

Version-Release number of selected component (if applicable):
3.6

How reproducible:
Always?

Steps to Reproduce:
1. Select a group of bugs, some with group privileges
2. Move them to a different product, choosing the "Don't change this group restriction" option.
  
Actual results:
Watch the group privileges disappear.


Expected results:
Group privileges should remain

Additional info:
This occurred when processing RT 152195.

  -- simon

Comment 1 Simon Green 2012-06-28 03:40:16 UTC

I have found out the cause of this, and have filled a bug upstream since it affects them. If they mark it as WONTFIX, then I'll carry the change locally since it definitely doesn't work as I would expect it to.

  -- simon

Comment 2 Simon Green 2012-06-28 06:21:56 UTC

So I proposed two options upstream, but have found flaws in both of them. I've proposed a third solution (bigger patch, but better solution IMO), but we are going to wait until LpSolit and dkl get online so they can add their 2¢ worth before I start writing a patch.

  -- simon

Comment 3 Simon Green 2012-06-29 03:33:47 UTC

It seems my third idea is the best one. I've written a patch for it and submitted it upstream. Will wait for them to approve it before putting it in our code base.

Comment 5 Simon Green 2012-07-05 23:33:13 UTC

Since this won't make the cut before 4.2.1-3 is released, I'm marking this as CLOSED/UPSTREAM. When (if) they include it in Bugzilla 4.2, we inherit the code that way.

  -- simon

Comment 6 Simon Green 2012-07-26 05:40:01 UTC

Upstream approved the patch, but rejected it for inclusion upstream. Therefore we will carry this change locally. Changed the estimate to one hour more to get the patch and make the recommended changes.

  -- simon