On 06/06/13 10: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.
Why do you want to create tickets (and at that point milestones, versions,
components) in the global environment anyway? I can only come up with cases
that could just as well be served by gathering them in a product.
Cheers,
Joe
I can see why there would be a desire to use global to contain tickets
but if we do not allow it, there doesn't appear to be a huge hardship in
forcing the users to create a product dedicated to the reason that they
wanted to.
The most common reasons for this might be to allow for users to raise
tickets associated with maintenance of the site itself but there is no
particular reason why this would be better than adding an 'infra'
product for instance. We do already allow for the global wiki to be used
as a base site wiki though we might even ask if there are more
appropriate ways of achieving this.
There might be questions of what to do about single product environments
as users may wonder at the point of a container in this situation.
Overall though, I'm leaning towards no tickets in global so that
effectively it is not even considered a product - it is just a container
with some shared resources.
Olemis - for what you want, do we need a means to fake a product where
the global product would be or something like that? What exactly is the
use-case? Can it effectively be achieved through webserver configuration?
Cheers,
Gary
