On 06.06.2013 11:40, Joachim Dreimann wrote: > On 6 June 2013 08:49, Matevž Bradač <[email protected]> wrote: > >> On 5. Jun, 2013, at 22:58, Olemis Lang wrote: >> >>> On 6/5/13, Matevž Bradač <[email protected]> wrote: >>>> On 5. Jun, 2013, at 21:17, Olemis Lang wrote: >>>> >>>>> Message subject is self-explanatory . Is it possible to create tickets >>>>> in the global environment ? How ? >>>> No. >>>> The global environment acts as a placeholder for all things global, >>>> e.g. actual products, users, repositories etc. Tickets, as well as >>>> components, versions etc. are all related to an actual product, it >>>> would serve no purpose to attach them to a global environment. >>>> >>> The global environment is yet another environment . Tickets et al. are >>> resources related to an environment , so I do not see a reason to not >>> to attach them to global env . >> It's true that it's another environment, but AFAIK it's treated a bit >> differently from product environments in the code, so you may run into >> issues. >> > I believe that 'global' _should_ be treated differently too. From a user's > perspective all products are siblings, global is a parent. When a parent > has the same properties as a sibling we're introducing new conceptual > complexities. That makes for great family intrigue novels, but not good > interaction design.
Hear, hear. Everyone please take your hacker hats off for this one; we do not want to explain to users about how "the global environment is just like a product environment except it's not." Tickets, components, etc. can only be created within a product; I see no good reason to complicate our lives by doing anything else, and lots of reasons against it. -- Brane -- Branko Čibej Director of Subversion | WANdisco | www.wandisco.com
