Bug 113179 - Incorrect component change error message when adding comment
Summary: Incorrect component change error message when adding comment
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General   
(Show other bugs)
Version: 3.2
Hardware: All
OS: Linux
medium vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-01-09 12:19 UTC by Kasper Dupont
Modified: 2013-06-24 02:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-04 21:44:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Kasper Dupont 2004-01-09 12:19:42 UTC
Description of problem:
Trying to add a comment to an existing bug #82651 on
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=82651 results in
the error message:
You tried to change the component field from AfterStep-APPS to kernel,
but only the owner or submitter of the bug, or a sufficiently
empowered user, may change that field.

Version-Release number of selected component (if applicable):

How reproducible:
Tried twince, happened both times.

Steps to Reproduce:
1. Try to add a comment to bug #82651
Actual results:
Error message

Expected results:
Comment added

Additional info:

Comment 1 David Lawrence 2006-04-08 17:51:53 UTC
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.

Comment 2 David Lawrence 2008-09-16 16:50:42 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.