You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Olemis Lang <ol...@gmail.com> on 2013/06/05 21:17:24 UTC

How to create tickets in global environment ?

Message subject is self-explanatory . Is it possible to create tickets
in the global environment ? How ?

AFAICS now REDIRECT_DEFAULT_RE in hooks.py will force some requests
sent to global env URL namespace to be processed in the context of
default product env . Therefore it seems to me that this is expected
behavior . Why ?

-- 
Regards,

Olemis.

Re: How to create tickets in global environment ?

Posted by Branko Čibej <br...@wandisco.com>.
On 06.06.2013 11:40, Joachim Dreimann wrote:
> On 6 June 2013 08:49, Matevž Bradač <ma...@digiverse.si> wrote:
>
>> On 5. Jun, 2013, at 22:58, Olemis Lang wrote:
>>
>>> On 6/5/13, Matevž Bradač <ma...@digiverse.si> 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


Re: How to create tickets in global environment ?

Posted by Olemis Lang <ol...@gmail.com>.
On 6/6/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> On 6 June 2013 14:41, Olemis Lang <ol...@gmail.com> wrote:
[...]
>> Anyway , please let's keep global env fully functional ;)
>>
>
> I think we all want to keep it fully functional, we just disagree what that
> functionality should be.
>
> If our current approach of a default product and redirections in order to
> not expose the product complexity to users when they first get set up
> causes too many issues, we should consider a different approach:
>

No need to , really . It's ok. In default BH installation let's keep
it the way it is . I just asked in first place mainly because I could
save a lot of time and trouble (rewriting functional test cases) if it
would be possible to create tickets in global env . My initial message
was not really a request for enhancement ;)

-- 
Regards,

Olemis.

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Olemis Lang <ol...@gmail.com>.
On 6/8/13, Branko Čibej <br...@wandisco.com> wrote:
> On 08.06.2013 00:46, Olemis Lang wrote:
>> On 6/7/13, Olemis Lang <ol...@gmail.com> wrote:
>>> On 6/7/13, Matevž Bradač <ma...@digiverse.si> wrote:
>>>> On 7. Jun, 2013, at 20:16, Gary Martin wrote:
>> [...]
>>>>> And another thing.. aren't we meant to have ticket numbers being used
>>>>> sequentially within each product? Would this break anything else?
>>>> The ticket id is an auto-incremented database key, so I don't think
>>>> that
>>>> would work.
>>> Unless we change the rules a bit ;) . Beyond that separate ticket ID
>>> sequences per-product should work ok
>>>
>> WRONG ! They won't work because ticket PK is it's ID , does not
>> include product .
>
> You are confusing an implementation detail (the database schema) and a
> user-visible feature. I never proposed to change the primary key of a
> ticket, as far as the schema and Trac internals are concerned.

I know ,  was replying to initial comment by Gary

> What I
> proposed was to have two ways to refer to the same ticket: the ticketid
> (which is the same as it always was), and another unique key consisting
> of (product-prefix, product-scoped-id). The key spaces are ismorphic.
>

... and JFTR in previous messages I just said I agree

[...]
>
> Here's how I would have expected the various ticket IDs to be assigned:
>
>
> Old ticket schema:
>
>     PRIMARY: (ticked-id) -> ticket
>
> New ticket schema:
>
>     PRIMARY: (ticket-id) -> ticket
>     UNIQUE:  (product-prefix, scoped-id) -> ticket
>

This is a very interesting suggestion . Nevertheless *if* products may
be moved back and forth from one product to the other then it seems to
me that a separate table still will be needed to track ticket IDs
per-product . OTOH it's possible to disallow such operation . and e.g.
make individual copies per-product.

<ot>
BTW, have we discussed anything about binding single ticket to
multiple (products / components) ?
</ot>

> Index mutation during multiproduct schema upgrade:
>
>     (ticket-id)   ->    (ticket-id)
>                         (default-product-prefix, ticket-id)
>
> Create new ticket in any product:
>
>     ticket-id = ticket_id_sequence.next
>     scoped-id = scoped_id_sequence[product_id].next
>
> URL construction (variant 1):
>
>     /ticket/<ticket-id> -> (default-product-prefix, ticket-id) -> ticket
>     /product/<prefix>/ticket/<scoped-id> -> (prefix, scoped-id) -> ticket
>     /ticket/<prefix>-<scoped-id> -> (prefix, scoped-id) -> ticket
>
> Or, alternatively (variant 2):
>
>     /ticket/<ticket-id> -> (ticket-id) -> ticket
>     /product/<prefix>/ticket/<scoped-id> -> (prefix, scoped-id) -> ticket
>     /ticket/<prefix>-<scoped-id> -> (prefix, scoped-id) -> ticket
>

JFTR , like I just said before, the impact of this change goes beyond
just chaging DB schema and URL paths. There's a need to patch our copy
of Trac to deal with (at least)

  - Ticket model
  - Resources

... and maybe also

  - Authz permissions
  - ... more TBD

[...]
>
> The reason I keep on yammering about this is because it's going to
> really, really suck if we can't maintain some kind of ticket identity
> when we import tickets from other systems, or even import trac
> environments into Bloodhound product environments. Ticket numbers appear
> all over the place, in mails, code comments, commit messages, IRC logs
> ... it's bad enough for a tracker URL to change, and IMO quite a bit
> worse if that change also changes the most unique part of the ticket
> identifier.
>

+

[...]

-- 
Regards,

Olemis.

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Gary Martin <ga...@wandisco.com>.
On 08/06/13 08:35, Branko Čibej wrote:
> On 08.06.2013 00:46, Olemis Lang wrote:
>> On 6/7/13, Olemis Lang <ol...@gmail.com> wrote:
>>> On 6/7/13, Matevž Bradač <ma...@digiverse.si> wrote:
>>>> On 7. Jun, 2013, at 20:16, Gary Martin wrote:
>> [...]
>>>>> And another thing.. aren't we meant to have ticket numbers being used
>>>>> sequentially within each product? Would this break anything else?
>>>> The ticket id is an auto-incremented database key, so I don't think that
>>>> would work.
>>> Unless we change the rules a bit ;) . Beyond that separate ticket ID
>>> sequences per-product should work ok
>>>
>> WRONG ! They won't work because ticket PK is it's ID , does not
>> include product .
> You are confusing an implementation detail (the database schema) and a
> user-visible feature. I never proposed to change the primary key of a
> ticket, as far as the schema and Trac internals are concerned. What I
> proposed was to have two ways to refer to the same ticket: the ticketid
> (which is the same as it always was), and another unique key consisting
> of (product-prefix, product-scoped-id). The key spaces are ismorphic.
>
> The fact that the upgrade to multiproduct makes the product-scoped-id
> for tickets in the default product the same as the ticket-ids is just an
> incidental consequence of our decision to maintain stable ticket URLs,
> that's all. And, I don't really care if tickets in other than the
> default product cannot be accessed through the shortened URLs --
> althrough I submit that a "default" product only makes sense in the
> context of the upgrade, and apart from that makes no sense at all.
>
> Here's how I would have expected the various ticket IDs to be assigned:
>
>
> Old ticket schema:
>
>      PRIMARY: (ticked-id) -> ticket
>
> New ticket schema:
>
>      PRIMARY: (ticket-id) -> ticket
>      UNIQUE:  (product-prefix, scoped-id) -> ticket
>
> Index mutation during multiproduct schema upgrade:
>
>      (ticket-id)   ->    (ticket-id)
>                          (default-product-prefix, ticket-id)
>
> Create new ticket in any product:
>
>      ticket-id = ticket_id_sequence.next
>      scoped-id = scoped_id_sequence[product_id].next
>
> URL construction (variant 1):
>
>      /ticket/<ticket-id> -> (default-product-prefix, ticket-id) -> ticket
>      /product/<prefix>/ticket/<scoped-id> -> (prefix, scoped-id) -> ticket
>      /ticket/<prefix>-<scoped-id> -> (prefix, scoped-id) -> ticket
>
> Or, alternatively (variant 2):
>
>      /ticket/<ticket-id> -> (ticket-id) -> ticket
>      /product/<prefix>/ticket/<scoped-id> -> (prefix, scoped-id) -> ticket
>      /ticket/<prefix>-<scoped-id> -> (prefix, scoped-id) -> ticket
>
>
> The second URL construction alternative would expose the ticket-id
> primary key in all URLs, allowing tickets in any product to be accesses
> through the shortened URL. The first alternative completely hides that
> primary key from the UI and URL space, but maintains the concept of a
> "default" product indefinitely.
>
> There is a third variant, a modification of variant 1, that allows the
> /ticket/<ticket-id> alias only for those tickets that existed during the
> schema upgrade. IMO that would even be the best alternative because it
> would not maintain the fiction that some default product is special
> other than during the upgrade.
>
> The reason I keep on yammering about this is because it's going to
> really, really suck if we can't maintain some kind of ticket identity
> when we import tickets from other systems, or even import trac
> environments into Bloodhound product environments. Ticket numbers appear
> all over the place, in mails, code comments, commit messages, IRC logs
> ... it's bad enough for a tracker URL to change, and IMO quite a bit
> worse if that change also changes the most unique part of the ticket
> identifier.
>
> (I'd even go as far as to say that Trac's exposing a datbase primary key
> as an application key is bad design, but let's leave that discussion for
> some other time. Suffice it to say that we have the perfect opportunity
> to fix that.)
>
> -- Brane
>

Brane is echoing my thinking pretty well. I am prepared to add to the 
yammering because I believe this is what we were meant to be aiming for.

As far as I am concerned we *require* that imported ticket ids remain 
the same on imports. Trac imports effectively set the requirement that 
we need the ability to have multiple #123 style links to maintain links 
that have already been used in the wiki, tickets and commit messages. 
Globally this is ambiguous but, within a product, the appropriate scope 
is implied.

Jira imports will be less problematic as scope is explicit but they will 
still require the ability to have continuous numbering within a product.

I'll try to avoid being opinionated on the URLs, at least for now.

Cheers,
     Gary

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Branko Čibej <br...@wandisco.com>.
On 08.06.2013 00:46, Olemis Lang wrote:
> On 6/7/13, Olemis Lang <ol...@gmail.com> wrote:
>> On 6/7/13, Matevž Bradač <ma...@digiverse.si> wrote:
>>> On 7. Jun, 2013, at 20:16, Gary Martin wrote:
> [...]
>>>> And another thing.. aren't we meant to have ticket numbers being used
>>>> sequentially within each product? Would this break anything else?
>>> The ticket id is an auto-incremented database key, so I don't think that
>>> would work.
>> Unless we change the rules a bit ;) . Beyond that separate ticket ID
>> sequences per-product should work ok
>>
> WRONG ! They won't work because ticket PK is it's ID , does not
> include product .

You are confusing an implementation detail (the database schema) and a
user-visible feature. I never proposed to change the primary key of a
ticket, as far as the schema and Trac internals are concerned. What I
proposed was to have two ways to refer to the same ticket: the ticketid
(which is the same as it always was), and another unique key consisting
of (product-prefix, product-scoped-id). The key spaces are ismorphic.

The fact that the upgrade to multiproduct makes the product-scoped-id
for tickets in the default product the same as the ticket-ids is just an
incidental consequence of our decision to maintain stable ticket URLs,
that's all. And, I don't really care if tickets in other than the
default product cannot be accessed through the shortened URLs --
althrough I submit that a "default" product only makes sense in the
context of the upgrade, and apart from that makes no sense at all.

Here's how I would have expected the various ticket IDs to be assigned:


Old ticket schema:

    PRIMARY: (ticked-id) -> ticket

New ticket schema:

    PRIMARY: (ticket-id) -> ticket
    UNIQUE:  (product-prefix, scoped-id) -> ticket

Index mutation during multiproduct schema upgrade:

    (ticket-id)   ->    (ticket-id)
                        (default-product-prefix, ticket-id)

Create new ticket in any product:

    ticket-id = ticket_id_sequence.next
    scoped-id = scoped_id_sequence[product_id].next

URL construction (variant 1):

    /ticket/<ticket-id> -> (default-product-prefix, ticket-id) -> ticket
    /product/<prefix>/ticket/<scoped-id> -> (prefix, scoped-id) -> ticket
    /ticket/<prefix>-<scoped-id> -> (prefix, scoped-id) -> ticket

Or, alternatively (variant 2):

    /ticket/<ticket-id> -> (ticket-id) -> ticket
    /product/<prefix>/ticket/<scoped-id> -> (prefix, scoped-id) -> ticket
    /ticket/<prefix>-<scoped-id> -> (prefix, scoped-id) -> ticket


The second URL construction alternative would expose the ticket-id
primary key in all URLs, allowing tickets in any product to be accesses
through the shortened URL. The first alternative completely hides that
primary key from the UI and URL space, but maintains the concept of a
"default" product indefinitely.

There is a third variant, a modification of variant 1, that allows the
/ticket/<ticket-id> alias only for those tickets that existed during the
schema upgrade. IMO that would even be the best alternative because it
would not maintain the fiction that some default product is special
other than during the upgrade.

The reason I keep on yammering about this is because it's going to
really, really suck if we can't maintain some kind of ticket identity
when we import tickets from other systems, or even import trac
environments into Bloodhound product environments. Ticket numbers appear
all over the place, in mails, code comments, commit messages, IRC logs
... it's bad enough for a tracker URL to change, and IMO quite a bit
worse if that change also changes the most unique part of the ticket
identifier.

(I'd even go as far as to say that Trac's exposing a datbase primary key
as an application key is bad design, but let's leave that discussion for
some other time. Suffice it to say that we have the perfect opportunity
to fix that.)

-- Brane

-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Olemis Lang <ol...@gmail.com>.
On 6/7/13, Olemis Lang <ol...@gmail.com> wrote:
> On 6/7/13, Matevž Bradač <ma...@digiverse.si> wrote:
>> On 7. Jun, 2013, at 20:16, Gary Martin wrote:
[...]
>>> And another thing.. aren't we meant to have ticket numbers being used
>>> sequentially within each product? Would this break anything else?
>>
>> The ticket id is an auto-incremented database key, so I don't think that
>> would work.
>
> Unless we change the rules a bit ;) . Beyond that separate ticket ID
> sequences per-product should work ok
>

WRONG ! They won't work because ticket PK is it's ID , does not
include product .

-- 
Regards,

Olemis.

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Olemis Lang <ol...@gmail.com>.
On 6/7/13, Matevž Bradač <ma...@digiverse.si> wrote:
> On 7. Jun, 2013, at 20:16, Gary Martin wrote:
>> On 06/06/13 14:51, Joachim Dreimann wrote:
>>> If our current approach of a default product and redirections in order
>>> to
>>> not expose the product complexity to users when they first get set up
>>> causes too many issues, we should consider a different approach:
>>>
>>> Simply asking users to set up their first product when they first launch
>>> Bloodhound.
>>>
>>> Then everything is always in products from the start, without the
>>> default
>>> product weirdness.
>>>
>>> - Joe
>>
>> The default product is certainly a bit weird anyway, particularly when it
>> is referenced with '@'.
>>
>> Actually, is it my imagination or does @-1 doesn't work as a ticket
>> reference anyway?

No, you'll need the long TracLinks expressions

>> Setting up a project with an appropriate name on first
>> launch or during setup seems like a good way to deal with this.
>
> It's already possible to do this when running bloodhound_setup.py, using
> the
> --default-product-prefix option. Maybe we should incorporate this as a step
> in the setup wizard as well?
>

Yes , please ; and require a name + prefix instead of choosing @ by default .

>>
>> And another thing.. aren't we meant to have ticket numbers being used
>> sequentially within each product? Would this break anything else?
>
> The ticket id is an auto-incremented database key, so I don't think that
> would work.

Unless we change the rules a bit ;) . Beyond that separate ticket ID
sequences per-product should work ok

[...]

-- 
Regards,

Olemis.

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Olemis Lang <ol...@gmail.com>.
On 6/7/13, Branko Čibej <br...@wandisco.com> wrote:
> On 07.06.2013 21:54, Matevž Bradač wrote:
>>
>>> And another thing.. aren't we meant to have ticket numbers being used
>>> sequentially within each product? Would this break anything else?
>> The ticket id is an auto-incremented database key, so I don't think that
>> would work.
>
> I thought we agreed a while ago that there are two ticket identifiers:
> the ticket-id, which is the same as in trac and the primary key of the
> ticket in the database; and the product-prefixed id, which is scoped
> within the product prefix and serves as an alias.
>

Once upon a time this looked ok to me.

> The reason for doing is this way should be obvious -- a) you maintain
> immutability of existing ticket URLs after multiproduct upgrade,

Even if this might be seen as a logical consequence , now in practice
it's not .

  1. In global context the DB cursor used to access
      ticket table is scoped to product=''
  2. AFAICS default hooks will redirect global /ticket/... requests
      onto default product (failing if not properly configured) .

So, unless I am missing something, the current situation consists in a
single ticket ID sequence (due to ticket DB auto inc field) not fully
accessible even in global scope

> and b)
> when you import a new product (from, e.g., Jira; or, e.g., Subversion's
> issue tracker) you can keep the same product-prefixed IDs regardless of
> the ticket-id primary key gets assigned to the database record. This is
> a very important property of ticket IDs, IMNSHO.
>

considering the fact that now ticket table's key is it's ID then there
are two options

  1. introduce another DB table to map product-specific
      ticket seq number to global seq number .
    * MP ticket module must be aware of this new table
    * also afaics it has an impact on other parts of the system
      including, but not limited to, milestones, authz permissions,
      wiki syntax , attachments, resources, ...
  2. upgrade ticket primary key to become (product, id)
    * afaics this choice has an impact on ticket module

I'd argue that it'd be nice to stick to option (2) , if feasible .

-- 
Regards,

Olemis.

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Branko Čibej <br...@wandisco.com>.
On 07.06.2013 21:54, Matevž Bradač wrote:
>
>> And another thing.. aren't we meant to have ticket numbers being used sequentially within each product? Would this break anything else?
> The ticket id is an auto-incremented database key, so I don't think that would work.

I thought we agreed a while ago that there are two ticket identifiers:
the ticket-id, which is the same as in trac and the primary key of the
ticket in the database; and the product-prefixed id, which is scoped
within the product prefix and serves as an alias.

The reason for doing is this way should be obvious -- a) you maintain
immutability of existing ticket URLs after multiproduct upgrade, and b)
when you import a new product (from, e.g., Jira; or, e.g., Subversion's
issue tracker) you can keep the same product-prefixed IDs regardless of
the ticket-id primary key gets assigned to the database record. This is
a very important property of ticket IDs, IMNSHO.

-- Brane


-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com

Re: Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Matevž Bradač <ma...@digiverse.si>.
On 7. Jun, 2013, at 20:16, Gary Martin wrote:

> On 06/06/13 14:51, Joachim Dreimann wrote:
>> If our current approach of a default product and redirections in order to
>> not expose the product complexity to users when they first get set up
>> causes too many issues, we should consider a different approach:
>> 
>> Simply asking users to set up their first product when they first launch
>> Bloodhound.
>> 
>> Then everything is always in products from the start, without the default
>> product weirdness.
>> 
>> - Joe
> 
> The default product is certainly a bit weird anyway, particularly when it is referenced with '@'.
> 
> Actually, is it my imagination or does @-1 doesn't work as a ticket reference anyway? Setting up a project with an appropriate name on first launch or during setup seems like a good way to deal with this.

It's already possible to do this when running bloodhound_setup.py, using the
--default-product-prefix option. Maybe we should incorporate this as a step
in the setup wizard as well?

> 
> And another thing.. aren't we meant to have ticket numbers being used sequentially within each product? Would this break anything else?

The ticket id is an auto-incremented database key, so I don't think that would work.
Also the links in the old format (wiki and URLs) should remain the same after upgrade
to multiproduct, since they may be referenced externally.
(see http://apache.markmail.org/thread/itozn4ui5f4ntrut)

> 
> Cheers,
>    Gary


Default product and ticket numbering (Was: Re: How to create tickets in global environment ?)

Posted by Gary Martin <ga...@wandisco.com>.
On 06/06/13 14:51, Joachim Dreimann wrote:
> If our current approach of a default product and redirections in order to
> not expose the product complexity to users when they first get set up
> causes too many issues, we should consider a different approach:
>
> Simply asking users to set up their first product when they first launch
> Bloodhound.
>
> Then everything is always in products from the start, without the default
> product weirdness.
>
> - Joe

The default product is certainly a bit weird anyway, particularly when 
it is referenced with '@'.

Actually, is it my imagination or does @-1 doesn't work as a ticket 
reference anyway? Setting up a project with an appropriate name on first 
launch or during setup seems like a good way to deal with this.

And another thing.. aren't we meant to have ticket numbers being used 
sequentially within each product? Would this break anything else?

Cheers,
     Gary

Re: How to create tickets in global environment ?

Posted by Joachim Dreimann <jo...@wandisco.com>.
On 6 June 2013 14:41, Olemis Lang <ol...@gmail.com> wrote:

> On 6/6/13, Gary Martin <ga...@wandisco.com> wrote:
> > On 06/06/13 10:40, Joachim Dreimann wrote:
> >> On 6 June 2013 08:49, Matevž Bradač <ma...@digiverse.si> wrote:
> >>> On 5. Jun, 2013, at 22:58, Olemis Lang wrote:
> [...]
> >>>> 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.
> [...]
> >
> > 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.
> >
>
> kind of ... in my deployments I'll need a *meta* environment and
> global seems to be a good target .
>
> > 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.
>
> IMHO , default should be ok in this case .
>
> > 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.
> >
>
> ... in any case I'll rethink everything for a while to see whether
> something like the infra product will be suitable .
>
> > 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?
> >
>
> One of the reasons is that (powered by custom bootstrap handlers)
> product's base URL is at subdomain.domain.tld whereas gobal's is at
> domain.tld so redirections to default product are problematic . Not
> the only issue I notice though .
>
> OTOH , when it comes to translating the functional test suite
> redirections make things a bit harder because there's a need to keep
> track of global vs default product context . That's beyond all other
> things that have changed in the UI and have an impact on functional
> testers as well <= /me working on fixing all this , and that's why I
> asked this question in first place
>
> Anyway , please let's keep global env fully functional ;)
>

I think we all want to keep it fully functional, we just disagree what that
functionality should be.

If our current approach of a default product and redirections in order to
not expose the product complexity to users when they first get set up
causes too many issues, we should consider a different approach:

Simply asking users to set up their first product when they first launch
Bloodhound.

Then everything is always in products from the start, without the default
product weirdness.

- Joe


> --
> Regards,
>
> Olemis.
>



-- 
Joachim Dreimann | *User Experience Manager*

WANdisco // *Non-Stop Data*

e. joachim.dreimann@wandisco.com
twitter @jdreimann <https://twitter.com/jdreimann>

Re: How to create tickets in global environment ?

Posted by Olemis Lang <ol...@gmail.com>.
On 6/6/13, Gary Martin <ga...@wandisco.com> wrote:
> On 06/06/13 10:40, Joachim Dreimann wrote:
>> On 6 June 2013 08:49, Matevž Bradač <ma...@digiverse.si> wrote:
>>> On 5. Jun, 2013, at 22:58, Olemis Lang wrote:
[...]
>>>> 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.
[...]
>
> 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.
>

kind of ... in my deployments I'll need a *meta* environment and
global seems to be a good target .

> 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.

IMHO , default should be ok in this case .

> 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.
>

... in any case I'll rethink everything for a while to see whether
something like the infra product will be suitable .

> 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?
>

One of the reasons is that (powered by custom bootstrap handlers)
product's base URL is at subdomain.domain.tld whereas gobal's is at
domain.tld so redirections to default product are problematic . Not
the only issue I notice though .

OTOH , when it comes to translating the functional test suite
redirections make things a bit harder because there's a need to keep
track of global vs default product context . That's beyond all other
things that have changed in the UI and have an impact on functional
testers as well <= /me working on fixing all this , and that's why I
asked this question in first place

Anyway , please let's keep global env fully functional ;)

-- 
Regards,

Olemis.

Re: How to create tickets in global environment ?

Posted by Gary Martin <ga...@wandisco.com>.
On 06/06/13 10:40, Joachim Dreimann wrote:
> On 6 June 2013 08:49, Matevž Bradač <ma...@digiverse.si> wrote:
>
>> On 5. Jun, 2013, at 22:58, Olemis Lang wrote:
>>
>>> On 6/5/13, Matevž Bradač <ma...@digiverse.si> 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

Re: How to create tickets in global environment ?

Posted by Joachim Dreimann <jo...@wandisco.com>.
On 6 June 2013 08:49, Matevž Bradač <ma...@digiverse.si> wrote:

>
> On 5. Jun, 2013, at 22:58, Olemis Lang wrote:
>
> > On 6/5/13, Matevž Bradač <ma...@digiverse.si> 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


>
> >
> > Anyway , in this case I asked because this breaks some assumptions
> > made by the functional test suite .
>
> Ok.
>
> >
> >>>
> >>> AFAICS now REDIRECT_DEFAULT_RE in hooks.py will force some requests
> >>> sent to global env URL namespace to be processed in the context of
> >>> default product env . Therefore it seems to me that this is expected
> >>> behavior . Why ?
> >>
> >> To "ease" the transition to multiproduct so to speak. Certain operations
> >> (such as creating a ticket) do not make sense in a global environment,
> >
> > IMO (at least sometimes) they do. Anyway I'll have to deal with this
> > in functional testing code.
>
> That would be best - since the global environment's name is an empty
> string,
> there may be assumptions made in the code which will not handle the global
> environment in the same manner.
>
> >
> >> so they are redirected to a default product instead.
> >
> > understood
> >
> >> Another option would be to hide/disable those operations in a global
> >> view, but I gather that wouldn't be such a simple task (UI overhaul,
> >> lots of messing around with templates etc.)
> >>
> >
> > Please do not do that . In some deployments I'll use the global
> > environment as usual , with tickets, wikis, ... everything .
>
> Oh I didn't mean this will actually be the case, just that it could've
> been implemented in that manner. (I would vote against that as well)
>
> >
> > --
> > Regards,
> >
> > Olemis.
>
>


-- 
Joachim Dreimann | *User Experience Manager*

WANdisco // *Non-Stop Data*

e. joachim.dreimann@wandisco.com
twitter @jdreimann <https://twitter.com/jdreimann>

Re: How to create tickets in global environment ?

Posted by Matevž Bradač <ma...@digiverse.si>.
On 5. Jun, 2013, at 22:58, Olemis Lang wrote:

> On 6/5/13, Matevž Bradač <ma...@digiverse.si> 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.

> 
> Anyway , in this case I asked because this breaks some assumptions
> made by the functional test suite .

Ok.

> 
>>> 
>>> AFAICS now REDIRECT_DEFAULT_RE in hooks.py will force some requests
>>> sent to global env URL namespace to be processed in the context of
>>> default product env . Therefore it seems to me that this is expected
>>> behavior . Why ?
>> 
>> To "ease" the transition to multiproduct so to speak. Certain operations
>> (such as creating a ticket) do not make sense in a global environment,
> 
> IMO (at least sometimes) they do. Anyway I'll have to deal with this
> in functional testing code.

That would be best - since the global environment's name is an empty string,
there may be assumptions made in the code which will not handle the global
environment in the same manner.

> 
>> so they are redirected to a default product instead.
> 
> understood
> 
>> Another option would be to hide/disable those operations in a global
>> view, but I gather that wouldn't be such a simple task (UI overhaul,
>> lots of messing around with templates etc.)
>> 
> 
> Please do not do that . In some deployments I'll use the global
> environment as usual , with tickets, wikis, ... everything .

Oh I didn't mean this will actually be the case, just that it could've
been implemented in that manner. (I would vote against that as well)

> 
> -- 
> Regards,
> 
> Olemis.


Re: How to create tickets in global environment ?

Posted by Olemis Lang <ol...@gmail.com>.
On 6/5/13, Matevž Bradač <ma...@digiverse.si> 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 .

Anyway , in this case I asked because this breaks some assumptions
made by the functional test suite .

>>
>> AFAICS now REDIRECT_DEFAULT_RE in hooks.py will force some requests
>> sent to global env URL namespace to be processed in the context of
>> default product env . Therefore it seems to me that this is expected
>> behavior . Why ?
>
> To "ease" the transition to multiproduct so to speak. Certain operations
> (such as creating a ticket) do not make sense in a global environment,

IMO (at least sometimes) they do. Anyway I'll have to deal with this
in functional testing code.

> so they are redirected to a default product instead.

understood

> Another option would be to hide/disable those operations in a global
> view, but I gather that wouldn't be such a simple task (UI overhaul,
> lots of messing around with templates etc.)
>

Please do not do that . In some deployments I'll use the global
environment as usual , with tickets, wikis, ... everything .

-- 
Regards,

Olemis.

Re: How to create tickets in global environment ?

Posted by Matevž Bradač <ma...@digiverse.si>.
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.

> 
> AFAICS now REDIRECT_DEFAULT_RE in hooks.py will force some requests
> sent to global env URL namespace to be processed in the context of
> default product env . Therefore it seems to me that this is expected
> behavior . Why ?

To "ease" the transition to multiproduct so to speak. Certain operations
(such as creating a ticket) do not make sense in a global environment,
so they are redirected to a default product instead.
Another option would be to hide/disable those operations in a global
view, but I gather that wouldn't be such a simple task (UI overhaul,
lots of messing around with templates etc.)

> 
> -- 
> Regards,
> 
> Olemis.

--
matevz