Bug 45911 - bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field
Summary: bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field
Status: RESOLVED WORKSFORME
Alias: None
Product: gcc
Classification: Unclassified
Component: web (show other bugs)
Version: unknown
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-06 16:40 UTC by Richard Henderson
Modified: 2013-11-23 00:04 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2011-11-16 00:00:00

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Henderson 2010-10-06 16:40:05 UTC 
Our bugzilla used to change the assign-to field away from
unassigned@gcc.gnu.org automatically.  Now you have to do
it in two steps.
Comment 1 Jonathan Wakely 2010-10-06 17:01:37 UTC 
Yes, I reported this in the bugzilla-test instance.
It would be useful to restore the "accept bug" button on UNCONFIRMED and NEW bugs which sets Status=ASSIGNED and AssignedTo=me
Comment 2 Frédéric Buclin 2011-03-07 22:52:57 UTC 
(In reply to comment #0)
> Our bugzilla used to change the assign-to field away from
> unassigned@gcc.gnu.org automatically.  Now you have to do
> it in two steps.

Correct, we did this change on purpose, upstream. See https://bugzilla.mozilla.org/show_bug.cgi?id=475409.
Comment 3 Jakub Jelinek 2011-03-07 22:58:23 UTC 
I don't mind if the two actions are split if the Asignee is somebody other than unassigned@gcc.gnu.org, but having a bug ASSIGNED to unassigned@gcc.gnu.org doesn't make any sense, and happens lately unfortunately very often.
Comment 4 Frédéric Buclin 2011-03-07 23:03:33 UTC 
The word "ASSIGNED" is confusing people, because it sounds like a synonym for the assignee field. In Bugzilla 4.0, we renamed ASSIGNED to IN_PROGRESS.
Comment 5 Jonathan Wakely 2011-03-07 23:46:05 UTC 
That just renames the state, it doesn't help address the logical flaw, which is that the fact a bug is being worked on and the person working on it are not independent.

Having an IN PROGRESS bug assigned to "noone" is no better than having an ASSIGNED bug assigned to "noone" - it still doesn't tell you who is doing the work in progress
Comment 6 Jason Merrill 2011-03-08 03:08:24 UTC 
Right.  Assigning a bug to myself and setting the status to Assigned/In Progress is a common enough action that there should be a shortcut so I don't need to type my email address in each time.
Comment 7 Jason Merrill 2011-03-30 17:35:04 UTC 
Red Hat bugzilla deals with this issue by having a "take" link next to the Assigned To field, after the "edit" link.
Comment 8 Jonathan Wakely 2011-11-16 10:56:52 UTC 
this is still needed, and I've noticed a few bugs in the last few days where someone has put themselves in the "Assigned" field but not changed the status to ASSIGNED.  It shouldn't be necessary to do both, a "take" shortcut is needed
Comment 9 Frédéric Buclin 2013-11-22 17:50:53 UTC 
The "take" link exists besides the Assignee field.
Comment 10 Jason Merrill 2013-11-23 00:04:54 UTC 
Yes, thanks.  Though it would be convenient if the 'take' link also changed the status from NEW or UNCONFIRMED to ASSIGNED.