[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Reverting Issuezilla policy from 'UNCONFIRMED/NEW' to '---/unscheduled'

From: Max Bowsher <maxb1_at_ukf.net>
Date: 2005-12-02 12:20:15 CET

Hash: SHA1

Max Bowsher wrote:
> A while ago, we switched from indicating 'untriaged issue' with
> target_milestone = '---', to status = UNCONFIRMED.
> This seemed like a good idea at the time, but unfortunately, CEE's
> current permissions setup really isn't friendly to this scheme.
> The problems:
> * Having the Observer role allows people to skip right past the
> UNCONFIRMED status during initial issue submission.
> * Having the Observer role allows people to change issues from
> UNCONFIRMED -> NEW, via a radio button marked "Confirm issue" - to those
> not already familiar with Bugzilla, it sounds like they _ought_ to do that.
> * Once an issue has been confirmed, there's no way to unconfirm it, if
> the confirmation was done erroneously.
> Therefore, it's time to go back to the old scheme:
> Issues are initially created with target_milestone = '---'. It is _not_
> possible to override this during initial issue submission.
> This value indicates 'untriaged'. It is set to something else
> ('unscheduled', if nothing is more appropriate, once triage is done).
> Observers are capable of changing the target_milestone, but the UI isn't
> such that it leads them to do it. For the very rare case when it is
> changed inappropriately, it will be noticed on the issues@ list, and can
> easily be undone.


Version: GnuPG v1.4.1 (Cygwin)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 2 12:21:54 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.