#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 starter
--------------------------+------------------------------------------------

Comment (by gjm):

 Replying to [comment:16 olemis]:
 > Replying to [comment:15 rjollos]:
 > >
 > [...]
 > > My preference is that the quick create does not have a milestone field
 because I like it to be centered around issue reporting, not issue
 scheduling,
 >
 > I think you are definitely right . Quick create ticket is for users
 reporting issues , whereas milestone field is for developers to schedule
 when this will be solved . So (unless developers = users , like we are ;)
 milestone field should not be there .

 I don't think that there is a distinction to be drawn between developers
 as users and any other situation. In general I would expect developers who
 raise tickets not to need to set a milestone either as it is quite likely
 that there will be a subset of users who are expected to decide when a
 ticket will be implemented.

 >
 > I wander what about priority field ?

 Priority should probably remain on the basis that it is fine for the
 reporter to immediately give the impression of how important it is for
 them. The alternative or complementary field, Severity, could also be used
 in this way of course.

 >
 > > but as others mentioned this is going to be based on user preference.
 >
 > I'd rather suggest not including it .

 Eventually we might have to consider including some kind of configuration
 for this but it might be better to wait for users to request this.

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

Reply via email to