[Bug web/45911] New: bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[Bug web/45911] New: bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[rth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

           Summary: bugzilla: Changing status to assigned no longer
                    auto-adjusts the assign-to field
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: web
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rth@gcc.gnu.org


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.

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[redi at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 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

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[LpSolit at netscape dot net]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

--- Comment #2 from Frédéric Buclin <LpSolit at netscape dot net> 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.

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jason at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 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.

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[LpSolit at netscape dot net]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

--- Comment #4 from Frédéric Buclin <LpSolit at netscape dot net> 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.

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[redi at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 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

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[jason at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> 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.

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[jason at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> 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.

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[redi at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011-11-16
                 CC|                            |redi at gcc dot gnu.org
     Ever Confirmed|0                           |1

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> 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

[Bug web/45911] bugzilla: Changing status to assigned no longer auto-adjusts the assign-to field

[jason at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45911

--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
Yes, thanks.  Though it would be convenient if the 'take' link also changed the
status from NEW or UNCONFIRMED to ASSIGNED.