On 21. Jun, 2013, at 9:46, Anze Staric wrote: > On Fri, Jun 21, 2013 at 9:23 AM, Matevž Bradač <[email protected]> wrote: > [...] >> IMO, if the default_product does not exist, we should: >> 1. check whether the preset default (@) exists and use that >> 2. if @ is not available, use the first product in the DB >> (and a warning to the user would also be nice) > > What about simply showing and error with message along the lines of > > Cannot create a ticket in non-existant product (product_prefix). > Please select different product or [link_to_create_new_product | > create product_prefix]. > > (assuming that user can select in which product the ticket gets created in).
Yes, in that case it would make sense. However this implies #569 is fixed first, but once that is done it will be impossible to trigger #568 anyhow if my understanding is correct. That is, the product dropdown will list all products from the DB (not including the default_product, since it's not stored in the DB), so the user will not be able to select the default_product at all.
