459802 - Can't (easily) give up an ASSI bug correctly

Status: NEW

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

In the past, with the radios at the bottom of the page, you could "give up" a bug by reassigning to defaults, and the bug status would revert from ASSI to NEW.  However, with the post-upgrade UI, you change assignee directly with a little (edit) link (either change it, or reset to default), and status is not touched.

I can't quite decide what the bug "really" is here:

a) Bug: Reassigning to default assignee should always reset ASSI to NEW (on bmo, this makes sense for the majority of components, as nobody@moz is the default assignee there, and nobody's bugs shouldn't ever be ASSI)

b) Enhancement: add a checkbox in the Assignee (edit) section that would allow you to "…and reset status to NEW" when changing assignee (allows reassigning to default to also change status, or allows someone else to give a bug away/take a bug from someone and not have the status remain ASSI)

c) Enhancement: The same as a, but called an "enhancement" because "you can still reset the status with a separate action at the same time you reset assignee to default" (to which I'd argue it's still a functional regression, since you never used to have to make a separate change to status, and people are pretty conditioned to that expectation) 

d) Bug: something else I've now forgotten while writing the rest of this report

I'm leaning towards Bug/a; if you're resetting to default, you're most likely not doing that to hand the bug to another developer (default owner) who's going to work on it right now (ASSI) but rather you're trying to give up the bug.

Comment 1

[Max Kanat-Alexander]

Mmm, yeah, I think (a) might make sense. It's something we'd do with JS in the frontend, not in the backend.

Comment 2

[Frédéric Buclin]

Keep in mind that bug statuses are no longer hardcoded. NEW may exist or not, same for ASSIGNED. So a) won't work; nor will b).

Comment 3

[Guy Pyrzak]

we could move this to bmo and then this would be a different story. The other more horrific option is we do something like we do with the duplicate resolution and have a parameter that is the "unassigned" status, in BMO's case it would be "NEW". I'm not sure if I'm a fan of this idea.