It was <2014-03-18 wto 10:47>, when Patrick Ohly wrote: > On Tue, 2014-03-18 at 09:45 +0100, Łukasz Stelmach wrote: >> However, I don't think such transition >> should be possible. Once a bug is assigned the only way for an assignee >> to get rid of it is to find a person who would take the responsibility. > > Suppose an issue was accidentally or, to phrase it more mildly, > tentatively assigned to someone. Perhaps the assigner wasn't sure which > developer would be able to take the issue. If the assigner picked the > wrong person,
This brings the problem of assignment. Some bugzillas I've worked with have been configured to assign bugs automatically based on other fields like project, component etc. How about this? When a bug is created it is unasigned. Then the default procedure for developers is to take unassigned bugs and assign to themselves. If they want to "give" a bug to sombody else they add that person as a watcher and write a request in the comments. > the assignee needs a way to reject the issue as quickly as > possible. Otherwise the issue seems fine (assigned) while in fact it > still needs an owner. Finding that owner is the job of the planners, > not that of individual developers. True. -- Łukasz Stelmach Samsung R&D Institute Poland Samsung Electronics
pgpIsxfHB8iU9.pgp
Description: PGP signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
