Red Hat Bugzilla – Bug 104434
Error message about component field when adding CC to bug report.
Last modified: 2013-06-23 23:01:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
Description of problem:
When I try to add myself as CC to a bug, I'm told:
"You tried to change the component field from AfterStep-APPS to
kdebase, but only the owner or submitter of the bug, or a
sufficiently empowered user, may change that field."
The component field is already set to "kdebase" and I'm not trying to change it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log in my account at bugzilla.redhat.com
2. Go to URL.
3. Select "Add Me to Cc List".
4. Click "Commit".
Actual Results: I get an error message about changing the component field.
Expected Results: I expected to be added to the CC list.
Using RHL9. I tried using both the Mozilla that comes with RHL9 and Mozilla
1.2.1 compiled separately.
I am closing this bug report as there has not been any activity on this for a
while and there has been various changes made to bugzilla in the meantime. If
the issue still exists, kindly reopen it. Thank you.
Sorry, it still happens. Now it says:
"You tried to change the Component field from kdebase to kdebase, but only the
owner or submitter of the bug, or a sufficiently empowered user, may change that
I don't remember if I've seen this happen with other bugs, but I have added
myself as CC to other bugs, so it doesn't always happen.
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.
It seems to work now, so I think you can close this bug report.
Thanks for verifying this is fixed. Closing.