On 21 June 2013 16:22, Olemis Lang <[email protected]> wrote: > On 6/21/13, Joachim Dreimann <[email protected]> wrote: > > On 21 June 2013 04:50, Apache Bloodhound <[email protected]> > wrote: > > > [...] > > > > I'd be grateful if you could tell me more about: > > 1. The use cases for a multi-domain deployment > > please see http://blood-hound.net > You'll notice a number of inconsistencies. I'll be submitting patches soon.
That doesn't actually answer my question; all I see is a Bloodhound Error page. I'm trying to learn under which circumstances a 'regular' Bloodhound deployment is not viable, and what makes a multi-domain deployment the best option at that point. > > 2. Why constraining ticket creation to the product a user currently views > > is better than offering a choice of products limited by permissions. > > > > That's not exactly what I meant in my comment . Notice that drop down > controls for ticket fields may be added / removed in configuration . > AFACIS that's the case too for product field (cmiiw) . My point is > *if* configuration won't display product combobox in QCT form then > target product MUST be set to current product , and if it is then it > MUST default to current product scope . > Ok, that's clearer. Thanks! - Joe > -- > Regards, > > Olemis. > -- Joachim Dreimann | *User Experience Manager* WANdisco // *Non-Stop Data* e. [email protected] twitter @jdreimann <https://twitter.com/jdreimann>
