[wp-meta] [Making WordPress.org] #6474: Core Trac: Revise "New Ticket" screen.

[Making WordPress.org]

#6474: Core Trac: Revise "New Ticket" screen.
-------------------------+---------------------
 Reporter:  costdev      |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:
Component:  Trac         |  Resolution:
 Keywords:  2nd-opinion  |
-------------------------+---------------------

Comment (by chealer):

 Looking at the current situation quickly, I am not so convinced. It would
 help if you could indicate/show which page starts your screencast.

 In the path I followed, it was excessively clear that the ITS was not
 meant for support questions; the form even goes as far as claiming “This
 is not for support.”🙄

 Can you provide a few recent examples of "support requests"
 inappropriately submitted as tickets?

 I disagree with your suggested form:
 1. There is too much overlap, for instance, between ''Security
 vulnerability'' and ''Bug''.
 2. It is unclear what you are supposed to do. For example, if you are
 experiencing a Gutenberg bug and wish to get help fixing it, do you use
 "Support request", "Bug", "Enhancement" or "Gutenberg"?

 That is not to say the current form is fine; clearly, defaulting ''Type''
 to ''defect (bug)'' is wrong.

 ''This comment and any other from myself on this ticket is offered under
 the terms of CC0 1.0.''

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/6474#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org