SF Tickets system

Currently we have four tickets systems for the project.  I'm thinking
of moving that to just one tickets system with a name of "Issues".
I've been working in the "Bugs" ticket system and would rename it to
"Issues".  I would then move the data from "Support Requests",
"Patches" and "Feature Requests" into the "Issues" ticket system as I
review those tickets.

Pros:
There is only one tickets system making the creation of tickets easier
for the user.
All patches one be in one tickets system, currently a patch can be in
any tickets system.

Cons:
I can't think of any other than the work involved and I'm already
doing that anyway.
Links in the archives and other tickets are already invalidated with
the SF upgrade so this is not an issue to consider.

Anyone else with Pros or Cons?

I plan to begin doing this work by Wednesday of next week.

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

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan