New fields in Issues tickets tracker.

I've added new fields in the Issues tracker I'll give below.  When
viewing the issues in lists and ticket view these fields will be
empty.  If you edit them the fields will take on default values and
should be changed to appropriate values before saving the change.

LABEL: VALUES

Type: Bugs Feature *Support Task
Patch attached: Boolean
Resolution: accepted duplicate fixed invalid later *none out-of-date
postponed rejected remind wont-fix works-for-me
Category: 64_bit_feature_request 64bit_readiness Aged_issue
Behaves_as_Documented component_package Duplicate Feature_in_WSL_4.0
Feature_in_WSL_4.1 Feature_requests Future_MSYS_enhancement
IINR_-_Include_In_Next_Release Invalid Invalid_mingw.ini Known_bugs
Known_Feature MinGW_Web_Site No_Documentation No_User_Response
OS_Version_No_Longer_Supported *Unknown Unreproducible
User_Environment_Issue User_Error Vista_Issue Waiting_User_Response

The * prefixing the value indicates the default.

I have removed the priority field.

Existing field Group a.k.a Milestone used to contain the values we
find in the Category field.  In the list of tickets you might see a
value of None or one of the values listed in the Category field.
Today the values for the Group field are MSYS, WSL, INSTALLER, OTHER,
and WEBSITE.  Unfortunately MSYS being first in that list is the
default.  I have a support ticket open asking some questions about
ordering or changing values.

I am not really liking the values for Resolution and Category;
especially Category we need to work on it.  Removing and changing
values will cause the tickets to retain the original value until the
ticket is edited.  At the time of edit, the editor would need to
ensure that an appropriate new value is chosen.  I would like ideas on
these two fields.  I will not do another mass edit for the values so
the old data will remain until someone actually needs to edit the
ticket.

There is a Label field for taxonomizing the ticket, when choosing the
OTHER group it is a good to state what the OTHER item is; e.g. gcc,
binutils, pexports, etc.  This gives the ability to search on like
issues by label.  To use this field you enter the taxonomy label which
can include spaces and press Enter/Return or a comma (maybe other
special character) to add the Label.  You need to click Save in order
to modify the ticket with a new Label.  This Label field can be used
with the other Groups as well so that like items can be labeled
together.  For example a Windows System Library (WSL) function is
causing someone grief, the name of the function can be entered as a
Label to group the tickets.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb