On 21 June 2013 04:50, Apache Bloodhound <[email protected]> wrote:
> #569: QCT view/edit link can direct to "Error: Invalid ticket number" > ---------------------------+-------------------- > Reporter: rjollos | Owner: nobody > Type: defect | Status: new > Priority: major | Milestone: > Component: multiproduct | Version: > Resolution: | Keywords: > ---------------------------+-------------------- > > Comment (by olemis): > > Replying to [comment:2 jdreimann]: > > Quick Ticket should never be scoped. I still firmly believe that scoping > of any of the main-nav, search and qct elements provides a predictably > confusing experience, not a predictably useful experience. > > > > I do not agree . Just consider a multi-domain deployment and scoping does > make sense . > I'd be grateful if you could tell me more about: 1. The use cases for a multi-domain deployment 2. Why constraining ticket creation to the product a user currently views is better than offering a choice of products limited by permissions. Thanks, Joe > > > We should simply default to the current product in the relevant drop > down within the quick ticket dialogue. > > I do want quick ticket form to be scoped considering active product > context, or at least default values set consistently. > > -- > Ticket URL: <https://issues.apache.org/bloodhound/ticket/569#comment:4> > Apache Bloodhound <https://issues.apache.org/bloodhound/> > The Apache Bloodhound issue tracker > -- Joachim Dreimann | *User Experience Manager* WANdisco // *Non-Stop Data* e. [email protected] twitter @jdreimann <https://twitter.com/jdreimann>
