On Mon, Jan 27, 2014 at 6:18 PM, Joachim Dreimann < [email protected]> wrote:
> > > On 27 Jan 2014, at 23:02, Ryan Ollos <[email protected]> wrote: > [...] > > > > We should reconsider whether it is a good design in light of recent > > changes. Given that tickets must be associated with a product, it make > > little sense to require that a user has `TICKET_CREATE` at global scope > in > > order for the QCT form to be available at global scope. The QCT would be > > more useful if a user could create a ticket in any product for which they > > have TICKET_CREATE permission, regardless of the permissions they have in > > the current scope (i.e. a the active environment). > > I agree with Ryan. That's how I believe QCT was intended to be used from > the beginning. It should only be hidden if the user has no ticket create > permissions in any product. > > This is not a trivial check (e.g. single SQL query ...) but it's performed anyway to filter products list . It makes sense , nonetheless it's not related to the goal of this ticket #388 . IMO there should be another one for this feature . -- Regards, Olemis - @olemislc
