Re: Removal of the 'empty' assign to entry.
Gianluca Sforna <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.mantis.general |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jun 3, 2009 at 11:07 AM, Jon Hardcastle <jd_hardcastle-/[email protected]> wrote: > Basically they want it arranged so that once an issue has been assigned to someone (i.e. responsibility is laid down) that either that person sees it through to testing/releasing or if they are no longer going to work on it - it is assigned to someone else. BUT when you update an issue it *is* possible to change the assignment field to blank i.e. no-one is now 'responsible' for that issue. In reality i dont envisage this happening much but they dont trust the dev's that much (it would seem) I guess the concern is with it not appearing on anyones 'my faults' list it might fall off the radar... I think the bug here is that it is possible to remove the assignee without moving back the status to something else (NEW or something, depending on your workflow) No bugs should be in the ASSIGNED state without someone on the "Assigned to" field -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get