Mailing-List: contact bloodhound-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Apache Bloodhound" <bloodhound-dev@incubator.apache.org>
Cc: bloodhound-commits@incubator.apache.org
Auto-Submitted: auto-generated
Date: Tue, 28 Aug 2012 09:50:24 -0000
Reply-To: bloodhound-dev@incubator.apache.org
Subject: Re: [Apache Bloodhound] #168: Include milestone field in quick
 create ticket form
Message-ID: <070.b5ef5f7bd743cb61a400750b3d155f86@incubator.apache.org>
References: <055.d6986024250c0307669ad4770737f1a6@incubator.apache.org>
In-Reply-To: <055.d6986024250c0307669ad4770737f1a6@incubator.apache.org>

#168: Include milestone field in quick create ticket form
--------------------------+----------------------------------------
  Reporter:  olemis       |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:
 Component:  ui design    |    Version:
Resolution:               |   Keywords:  quick create ticket fields
--------------------------+----------------------------------------

Comment (by jdreimann):

 I believe asking for both Version and Milestone is contra-productive. The
 idea behind asking for Version only was that it's a more fuzzy indicator,
 which users could make a quick decision about. This may be more true for
 Milestones, so we could ask for those instead, rather than in addition to
 Versions.

 Another option would be to drop that selector entirely, if it doesn't help
 with the review of incoming tickets significantly enough.

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/168#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker