On 3. Apr, 2013, at 8:49, Olemis Lang wrote: > On 4/2/13, Matevž Bradač <[email protected]> wrote: >> On 2. Apr, 2013, at 16:28, Gary Martin wrote: >> >>> On 02/04/13 12:34, Jure Zitnik wrote: >>>> On 3/29/13 11:58 AM, Gary Martin wrote: >>>>> Yeah, looking forward to it! >>>>> >>>>> On 29/03/13 10:43, Andrej Golcov wrote: >>>>>> +1 to go for it. >>>> >>>> fyi, branch BEP-0003 (multi product) has been merged to trunk in >>>> r1463489, reintegrated branch has been removed in r1463491. >>>> >>>> Cheers, >>>> Jure >>>> >>>> >>> >>> I am finding that I don't get tickets created properly when I try to >>> create one with the Create Ticket dropdown from the front page (so not in >>> default or other products). Is this expected? Once in the products/%40/ >>> area things seem to work again. >>> >>> Cheers, >>> Gary >> >> For the time being this is expected yes, some UX/UI things still have to be >> polished, e.g.: >> - global/product-scoped links and their behaviour (wiki, queries, ticket >> relations) >> - which operations should be allowed in which scope (i.e. your create ticket >> example) > > I'll try to reproduce Gary's «issue» in a test case . Will post by tomorrow . > >> - some fixes to the global dashboard >> etc. >> >> There are also a couple of regressions wrt. the multiproduct branch, those >> should probably >> be fixed first (e.g. PRODUCT_XXX permissions not set/copied when creating a >> new product). >> > > The permissions policy developed in #438 will grant product owner with > PRODUCT_ADMIN permission even if not assigned explicitly . Maybe there > is a good reason to add that permission in product perms store too , > but not strictly necessary . > > Is there anything else to do about this ?
It seems so - when creating a new product, the product is created but cannot be viewed due to PRODUCT_VIEW permissions missing. Note that this only happens with newly created products, the default one (@) works as it is. There are no PRODUCT_XXX permissions in the permission table for either of them(which should be okay). I haven't found the root cause yet, still checking the code. On another note, a product need not have an owner (and IIRC that's the default behaviour), how should the permission policy behave in that case? -- matevz > >> And last but not least, upgrading existing installations (both Trac and BH) >> is also >> something to be more extensively tested. >> > > + > > -- > Regards, > > Olemis.
