This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
bugzilla
- From: Marco Trudel <mtrudel at gmx dot ch>
- To: GCC Java <java at gcc dot gnu dot org>
- Date: Tue, 30 Jan 2007 11:26:09 +0100
- Subject: bugzilla
Hey Guys
I always had problems with the bugzilla:
When I try to add a comment to a bug from someone else, I write my
comment to the field and press Commit. I then usually get:
You tried to change the Assignee field from unassigned@gcc.gnu.org to
__UNKNOWN__, but only the assignee of the bug, or a sufficiently
empowered user may change that field.
The solution is - if I remember right - to select "Reassign bug to
default assignee of selected component".
Now I tried to make a comment to a reopened bug but I can't since there
is no option that works. I entered my comment, selected "Add to CC list"
and this are the errors:
- Leave as REOPENED -> this one should work, shouldn't it?
You tried to change the Assignee field from unassigned@gcc.gnu.org to
__UNKNOWN__, but only the assignee of the bug, or a sufficiently
empowered user may change that field.
- Accept bug (change status to ASSIGNED)
I did not try that since I definitely don't ant that to happen.
- Mark bug as waiting for feedback
I did not try that since I definitely don't ant that to happen.
- Mark bug as suspended
I did not try that since I definitely don't ant that to happen.
- Resolve bug, changing resolution to ...
I did not try that since I definitely don't ant that to happen.
- Resolve bug, mark it as duplicate of bug #
I did not try that since I definitely don't ant that to happen.
- Reassign bug to unassigned@gcc.gnu.org
You tried to change the Status field from REOPENED to NEW, but only the
assignee or reporter of the bug, or a sufficiently empowered user may
change that field.
- Reassign bug to default assignee of selected component
You tried to change the Status field from REOPENED to NEW, but only the
assignee or reporter of the bug, or a sufficiently empowered user may
change that field.
So, what am I doing wrong. This can't be broken, can it? There are too
much people using it...
Marco