Bug 1487659

Summary:	Bugzilla: Missing permissions for bug reporting/maintenance
Product:	[Retired] Fedora Documentation	Reporter:	Woi <woiling>
Component:	release-notes	Assignee:	Release Notes Tracker <relnotes>
Status:	CLOSED EOL	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	relnotes, wb8rcr, zach
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:	2019-11-07 15:30:05 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 Woi 2017-09-01 14:15:18 UTC

Description of problem:

I now and then miss necessary permissions for bug reports or updates. For example I'm not allowed to change the version field or add keywords.
In addition I was unable to find any documentation about the default permissions of users, of Fedoras Bugzilla nor on how to proceed with issues like this. (See Bug #1487287 for my first attempt to get support with this)  


How reproducible:

Steps to Reproduce:
1. Login to RH bugzilla as me ^^ (Maybe just create a new user and login)
2a. Try to add "CommonBugs" to the keywords of Bug #1441920
2b. Try to change version field of Bug #1259549 to 26
3. Notice the missing permissions to do so.

Actual results:
There is no way to change certain fields of bug reports for me (and assumable for default users)

Expected results:
At least the keyword field can be edited as suggested here:
http://fedoraproject.org/wiki/Common_F26_bugs#My_bug_is_not_listed

Comment 1 Woi 2017-09-17 23:30:09 UTC

Another example is Bug #1374051 where users are not allowed to reopen after auto close

Comment 2 Petr Bokoc 2019-11-07 15:30:05 UTC

I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.