116488 - Auto-Assign Self Entered Bugs

Status: RESOLVED WONTFIX

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[Mike Todd]

When entering a new bug and the bug "reporter" is the same as "assigned to" 
(i.e. you entered the bug for yourself), Bugzilla should automatically mark the 
bug ASSIGNED instead of NEW.

This is just one of those small annoyances.

Comment 1

[Mike Todd]

Attachment: Patch to allow new posts to be assigned to the originator. When applied to post_bug.cgi

Attached is a patch to facilitate this fix:
This patch should be applied to post_bug.cgi

Note this does not work with the Initial State: NEW/UNCONFIRMED option enabled.

Comment 2

[Dave Miller [:justdave]]

This sounds like a good idea...   I think we need a little more discussion on
logistics though...  as stated the attached patch doesn't work if you have
UNCONFIRMED enabled and the reporter has "canconfirm" privileges (which would
most likely be the people wanting to self-assign things they report if you think
about it).  Before we fix the patch though, how would we deal with that from a
UI standpoint?  Allow "ASSIGNED" as an option in the "state of the new bug"
popup as well as "UNCONFIRMED" and "NEW", but then complain if they set it to
ASSIGNED and the reporter isn't the assignee?  This sounds like asking for
trouble to do it that way, but I'm not sure how else you could...

Comment 3

[Christopher Aillon (sabbatical, not receiving bugmail)]

I just thought about this today actually, and was going to file but I found this.

Anyway here is my thoughts on this:

For users without canconfirm:
   File in an unconfirmed state always.

For users with canconfirm:
   Have the NEW and UNCO options as current, but just assume that if the
reporter is the owner, and the original state is NEW as selected, it will be
auto-upgraded to ASSI.  If it ever changes owners, it'll revert to new.

There is no need to complicate the UI with an ASSI drop down that won't work
most of the time.

Comment 4

[Matthew Tuck [:CodeMachine]]

We have to remember that people use ASSIGNED in different ways.  Not everyone is
going to want to auto assign.  I suggest we wait until we fix the ASSIGNED
debacle by doing customised statuses (bug #101179) and consider what we need to
fix this as a part of that.

Comment 5

[Bradley Baetz (:bbaetz)]

Comment on attachment 62591 [details] [diff] [review]
Patch to allow new posts to be assigned to the originator.  When applied to post_bug.cgi

This patch looks odd (it doesn't have a header). Plus I don't think we should
do this unconditionally anyway - sometimes I fiel a bug, but will push it off
to future, and so its not relaly assigned.

Comment 6

[Stephen Lee]

IMHO this should model the eventual UI for Bug 35195, and similar functionality 
should be available on each (new bug or existing bug being reassigned).

In other words, reassigning an existing UNCONFIRMED bug and filing a new bug 
should offer the same set of possible status transitions. (i.e. if bug 35195 
allows you to reassign a bug to a 3rd party and accept it in one go, the same 
should be possible here, and vice-versa).


For that matter, what about other possible initial status values:

- trivial fixes where the bug is found by observing the incorrect code that you 
fix while you're there...
"While I was doing the changes for bug XYZ I noticed this uninitialised pointer 
that will cause this fault in this situation. Now FIXED".
... in that case you could argue that the bug should be able to be filed in 
a "RESOLVED FIXED" state! :-)

- I'm sure suitably contrived situations could be invented for INVALID, 
WONTFIX, and WORKSFORME too.....

Comment 7

[Dave Miller [:justdave]]

Comment on attachment 62591 [details] [diff] [review]
Patch to allow new posts to be assigned to the originator.  When applied to post_bug.cgi

marking the review- that was implied in comments 4, 5 and 6

Comment 8

[Dave Miller [:justdave]]

enhancements without a current patch are getting pushed to 2.20

Comment 9

[Dave Miller [:justdave]]

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.

Comment 10

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 11

[Frédéric Buclin]

Bug statuses are no longer hardcoded since Bugzilla 3.2, and so we cannot reasonable enforce any rule on an editable field value. Moreover, ASSIGNED is gone in the new Bugzilla 4.x workflow anyway. As said in this bug, not everybody would want this feature anyway and so it doesn't worth the code complexity.