1226862 - Setting owner should change status of NEW or UNCONFIRMED to ASSIGNED

Status: RESOLVED DUPLICATE of bug 933033

(bugzilla.mozilla.org :: Bug Creation/Editing, defect)

Description

[Adrian Aichner [:anaran]]

See:

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=NOT%20owner%3Anobody%40mozilla.org%20AND%20NOT%20status%3ARESOLVED%20AND%20NOT%20status%3AREOPENED%20AND%20NOT%20status%3AASSIGNED%20AND%20NOT%20status%3AVERIFIED&list_id=12696530

Details:

As shown by above query a great many assigned bugs are left in states NEW or UNCONFIRMED just because the manual status change is forgotten.

This makes them all look neglected when the owner field is not shown or not taken into account.

Seems like a valuable/visible improvement to me because it sends a more engaging message to bug reporters.

http://mzl.la/1vxCDgA

Comment 1

[:glob ✱]

setting the assignee of a bug doesn't necessarily mean they are working on it.

because different teams use bugzilla differently, we can't impose a process-related automation without breaking things, and your proposal breaks a very common process:

- a bug's assignee is set to put it into that person's "queue", or to otherwise indicate they will be working on it
- when they actually start working on it, the person sets the bug to ASSIGNED

Comment 2

[Adrian Aichner [:anaran]]

Thanks for the explanation, Byron. I had not thought of that use case.

Would it be possible for the bugzilla UI to ask in some way on [Save Changes], when the assignee field gets set, whether the bug should be moved to ASSIGNED state right away?

I am pretty sure that a good portion of assigned bugs remain in state NEW or UNCONFIRMED by accident or neglect, even as they are actively being worked on.

Comment 3

[:glob ✱]

once the overall process for bugs has been figured out (the new bugmaster is tasked with that), then i'm happy to look at streamlining the recommended workflow.