Bug 104434
Summary: | Error message about component field when adding CC to bug report. | ||
---|---|---|---|
Product: | [Community] Bugzilla | Reporter: | Alexander Boström <abo> |
Component: | Bugzilla General | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.2 | CC: | sundaram |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
URL: | https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=86494 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-09-17 14:33:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexander Boström
2003-09-15 15:46:13 UTC
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 field." 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. Dave |