Bug 882165

Summary:	need to enhance the restrictions for reopening a 'CLOSED/ERRATA' bug of RHEL product
Product:	[Community] Bugzilla	Reporter:	wangjing <jingwang>
Component:	Creating/Changing Bugs	Assignee:	Simon Green <sgreen>
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2	CC:	ebaak
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-17 03:00:53 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 wangjing 2012-11-30 10:16:57 UTC

Description of problem:
a redhat account(not admin) can reopen a 'CLOSED/ERRATA' bug of RHEL product by changing the resolution from 'ERRATA' to others.

Version-Release number of selected component (if applicable):
version 4.2.4-7.b01 qe test env

How reproducible:
always

Steps to Reproduce:
1.create a  bug for RHEL, and set status to 'CLOSED/ERRATA'.
2.login with a user who is not in 'admin' group but in red hat internal group.
3.open the bug(step1) and try to change its status to 'ASSIGNED'.
4.change the resolution from 'ERRATA' to 'NOTABUG'.
5.try to change its status to 'ASSIGNED'.
  
Actual results:
after step3:A redhat user who is not in 'admin' group can not reopen a 'CLOSED/ERRATA' bug of product RHEL.
after step5:the bug was reopened in the end.

Expected results:
after step4:the resolution cannot be changed also.
A redhat user who is not in 'admin' group can not reopen a 'CLOSED/ERRATA' bug of product RHEL.

Additional info:
bug 406141 was 'closed NEXTRELEASE' in 2008, on current version the feature just affect RHEL product, not RHEL Beta, RHEL Public Beta, it's different from the 'Description' of bug 406141, so add another bug for this.

Comment 1 Simon Green 2012-12-17 03:00:53 UTC


*** This bug has been marked as a duplicate of bug 822804 ***