> 1. adds 'default' product > This is the product to which all tickets that don't have product set are > migrated. As there won't be any global tickets, each ticket needs to be in a > product, so this is where all tickets w/o product set will end up after the > upgrade. The prefix, name and description are currently set to 'default', > 'Default' and 'Default product' respectively. Open question remains what > happens if there's a product with the same name already defined in the > database. Any suggestions? My suggestion is to keep things simple here: if there is already product named "Default', let's assign global tickets to this product. There should be reason why this product was called "Default" :)
Regards, Andrej
