Open Bug 663855 Opened 13 years ago Updated 9 years ago

Auto-assign unowned bugs when attaching patches

Categories

(Bugzilla :: Attachments & Requests, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: dao, Unassigned)

References

Details

(Whiteboard: [wanted-bmo])

There's a "take bug" checkbox when creating an attachment -- It would be great if this could be checked automatically (allowing the user to opt out) when the attachment is a patch and the bug is unowned (i.e. assigned to the default assignee).

Also, when attaching a patch right away when filing a bug, the "take bug" checkbox doesn't exist, requiring users to manually fill the assignee field. Ideally the checkbox would exist there as well and behave as described above.

(I'm not sure if what I'm asking for would be a core bugzilla feature or a bugzilla.mozilla.org extension.)
It seems sensible to auto-assign the bug when the attachment is a patch, but it would have to be a bmo customization, since "unassigned" is a concept that doesn't exist upstream (although it very likely will, someday).
Couldn't this just be an option based on the default assignee? Individual installations could then activate it in case they have dummy default assignees such as nobody@mozilla.org or create-and-change@bugzilla.bugs.
Sure, checking if the assignee is currently the default could possibly work, yeah.
Assignee: create-and-change → attach-and-request
Component: Creating/Changing Bugs → Attachments & Requests
Priority: -- → P3
Blocks: 707673
No longer blocks: 707673
Whiteboard: [wanted-bmo]
(In reply to Max Kanat-Alexander from comment #3)
> Sure, checking if the assignee is currently the default could possibly work,
> yeah.

I see several problems to this:

First of all, many teams in small Bugzilla installations have already configured components to point to the correct assignee by default. So this doesn't match the definition of "unassigned". In that case, you probably don't want to see the bug being reassigned to someone else just because he proposed a fix.

Secondly, a powerless user could abuse Bugzilla by attaching a patch to a bug to take ownership of that bug, and then being able to edit all bug fields as he would be the new assignee. The feature should then only be limited to users with editbugs privs, to prevent abuse and to not have to deal with validators to allow this scenario.

The last point makes me think that this feature becomes less useful as users with editbugs privs can already very easily take ownwership by clicking the "take bug" checkbox.
You need to log in before you can comment on or make changes to this bug.