Bug 1434068

Summary:	Need to fix BZ perms for external contributors
Product:	[Community] GlusterFS	Reporter:	Jeff Darcy <jeff>
Component:	project-infrastructure	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-infra, jeff, ndevos
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-28 12:19:07 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 Jeff Darcy 2017-03-20 16:39:56 UTC

After filing bug 1434062, I went to assign it to myself as I normally would.  Apparently, since I'm no longer a Red Hat employee, I can't assign bugs (even to myself) or set their status other than to NEW/CLOSED.  This needs to be fixed not only for myself but in general so that external contributors can actually follow the process Red Hat has mandated that they follow.

Comment 1 Niels de Vos 2017-03-20 22:30:07 UTC

I'll request this for you at the Red Hat Bugzilla team. Other contributors already have these permissions too.

Comment 2 Jeff Darcy 2017-03-20 23:45:27 UTC

Thanks, Niels.

Comment 3 Niels de Vos 2017-03-21 12:52:18 UTC

Jeff, please check if you can close this now. Maybe you need to logout/login into Bugzilla before the permissions get applied to your session.

Comment 4 Niels de Vos 2017-03-28 12:19:07 UTC

Jeff confirmed that this was addressed and has the options now.