You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@bloodhound.apache.org by Tim Tisdall <ti...@gmail.com> on 2013/06/04 20:04:11 UTC
multi-product components?
I see how to enter different products and I see how to enter components.
However, shouldn't the components be dependent on a particular product?
For example, if I have products such as "database" and "game" and
components "joystick control" and "btree indexes". When I create a ticket
for the "game" product I don't think I should be able to select "btree
indexes".
Or am I not understanding the intended use of those categories?
-Tim
Re: multi-product components?
Posted by Olemis Lang <ol...@gmail.com>.
On 6/5/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> On 5 June 2013 17:11, Tim Tisdall <ti...@gmail.com> wrote:
>
>> k.. I'll wait for the next version then. I tried manually adding
>> /products/someproduct into my URL but it didn't seem to make any
>> difference
>> when creating new components. I'm guessing the multiproduct support just
>> isn't complete in 0.5.3.
>>
>> -Tim
>>
>
> You're right, 0.5.3 came out shortly after we just had a basic
> implementation. There has been a lot of progress since. We've taken
> unusually long to get 0.6 released, but the vote for it will likely happen
> in the next few days.
>
JFTR , the fact that it took so long to release a new version after
0.5.3 also means that major improvements and new features will be
offered; one of them being the actual separation of resources (<=
everything e.g. wiki , components, milestones, permissions, ...)
per-product.
--
Regards,
Olemis.
Re: multi-product components?
Posted by Joachim Dreimann <jo...@wandisco.com>.
On 5 June 2013 17:11, Tim Tisdall <ti...@gmail.com> wrote:
> k.. I'll wait for the next version then. I tried manually adding
> /products/someproduct into my URL but it didn't seem to make any difference
> when creating new components. I'm guessing the multiproduct support just
> isn't complete in 0.5.3.
>
> -Tim
>
You're right, 0.5.3 came out shortly after we just had a basic
implementation. There has been a lot of progress since. We've taken
unusually long to get 0.6 released, but the vote for it will likely happen
in the next few days.
- Joe
>
>
> On Wed, Jun 5, 2013 at 11:52 AM, Olemis Lang <ol...@gmail.com> wrote:
>
>> Hi Tim !
>>
>> On 6/5/13, Tim Tisdall <ti...@gmail.com> wrote:
>> > I'm not sure where something is going wrong or what's by design so I'll
>> > just describe what I've done and hopefully it will become apparent.
>> >
>> > I added 2 products under the Apps > Products . I then went to add
>> > components under Apps > Admin > Components. That screen just gives two
>> > fields which is "Name" and "Owner". I assumed that "Owner" was a
>> > particular user account as the initial content had components with the
>> > owner "somebody" (if I remember correctly). I don't see any where that
>> I
>> > can input what component goes with what product either on the
>> components or
>> > products screens.
>> >
>> > When creating a ticket I can choose any combination of Product and
>> > Component and there's no restrictions.
>> >
>>
>> When creating components and other resources (e.g. wiki pages) they
>> are bound to the current product context . In default Bloodhound
>> installations it's determined by product prefix immediately after
>> /products in URL e.g. product=myproduct in
>> /products/myproduct/admin/ticket/component .
>>
>> In most recent versions you may also add components using trac-admin this
>> way
>>
>> {{{
>> #!sh
>>
>> $ trac-admin /path/to/bh/env product admin myproduct component add
>> mycomponent theowner
>>
>> }}}
>>
>> ... but maybe this is off-topic because it seems you are running 0.5.3
>> . Multi-product support in trunk should be improved with respect to
>> what we offered in 0.5.x . New release coming soon including such
>> changes.
>>
>> --
>> Regards,
>>
>> Olemis.
>>
>
>
--
Joachim Dreimann | *User Experience Manager*
WANdisco // *Non-Stop Data*
e. joachim.dreimann@wandisco.com
twitter @jdreimann <https://twitter.com/jdreimann>
Re: multi-product components?
Posted by Tim Tisdall <ti...@gmail.com>.
k.. I'll wait for the next version then. I tried manually adding
/products/someproduct into my URL but it didn't seem to make any difference
when creating new components. I'm guessing the multiproduct support just
isn't complete in 0.5.3.
-Tim
On Wed, Jun 5, 2013 at 11:52 AM, Olemis Lang <ol...@gmail.com> wrote:
> Hi Tim !
>
> On 6/5/13, Tim Tisdall <ti...@gmail.com> wrote:
> > I'm not sure where something is going wrong or what's by design so I'll
> > just describe what I've done and hopefully it will become apparent.
> >
> > I added 2 products under the Apps > Products . I then went to add
> > components under Apps > Admin > Components. That screen just gives two
> > fields which is "Name" and "Owner". I assumed that "Owner" was a
> > particular user account as the initial content had components with the
> > owner "somebody" (if I remember correctly). I don't see any where that I
> > can input what component goes with what product either on the components
> or
> > products screens.
> >
> > When creating a ticket I can choose any combination of Product and
> > Component and there's no restrictions.
> >
>
> When creating components and other resources (e.g. wiki pages) they
> are bound to the current product context . In default Bloodhound
> installations it's determined by product prefix immediately after
> /products in URL e.g. product=myproduct in
> /products/myproduct/admin/ticket/component .
>
> In most recent versions you may also add components using trac-admin this
> way
>
> {{{
> #!sh
>
> $ trac-admin /path/to/bh/env product admin myproduct component add
> mycomponent theowner
>
> }}}
>
> ... but maybe this is off-topic because it seems you are running 0.5.3
> . Multi-product support in trunk should be improved with respect to
> what we offered in 0.5.x . New release coming soon including such
> changes.
>
> --
> Regards,
>
> Olemis.
>
Re: multi-product components?
Posted by Olemis Lang <ol...@gmail.com>.
Hi Tim !
On 6/5/13, Tim Tisdall <ti...@gmail.com> wrote:
> I'm not sure where something is going wrong or what's by design so I'll
> just describe what I've done and hopefully it will become apparent.
>
> I added 2 products under the Apps > Products . I then went to add
> components under Apps > Admin > Components. That screen just gives two
> fields which is "Name" and "Owner". I assumed that "Owner" was a
> particular user account as the initial content had components with the
> owner "somebody" (if I remember correctly). I don't see any where that I
> can input what component goes with what product either on the components or
> products screens.
>
> When creating a ticket I can choose any combination of Product and
> Component and there's no restrictions.
>
When creating components and other resources (e.g. wiki pages) they
are bound to the current product context . In default Bloodhound
installations it's determined by product prefix immediately after
/products in URL e.g. product=myproduct in
/products/myproduct/admin/ticket/component .
In most recent versions you may also add components using trac-admin this way
{{{
#!sh
$ trac-admin /path/to/bh/env product admin myproduct component add
mycomponent theowner
}}}
... but maybe this is off-topic because it seems you are running 0.5.3
. Multi-product support in trunk should be improved with respect to
what we offered in 0.5.x . New release coming soon including such
changes.
--
Regards,
Olemis.
Re: multi-product components?
Posted by Tim Tisdall <ti...@gmail.com>.
I'm not sure where something is going wrong or what's by design so I'll
just describe what I've done and hopefully it will become apparent.
I added 2 products under the Apps > Products . I then went to add
components under Apps > Admin > Components. That screen just gives two
fields which is "Name" and "Owner". I assumed that "Owner" was a
particular user account as the initial content had components with the
owner "somebody" (if I remember correctly). I don't see any where that I
can input what component goes with what product either on the components or
products screens.
When creating a ticket I can choose any combination of Product and
Component and there's no restrictions.
On Wed, Jun 5, 2013 at 4:44 AM, Matevž Bradač <ma...@digiverse.si> wrote:
> On 4. Jun, 2013, at 20:04, Tim Tisdall wrote:
>
> > I see how to enter different products and I see how to enter components.
> However, shouldn't the components be dependent on a particular product?
>
> Indeed they should be.
>
> >
> > For example, if I have products such as "database" and "game" and
> components "joystick control" and "btree indexes". When I create a ticket
> for the "game" product I don't think I should be able to select "btree
> indexes".
>
> You are correct - if the "btree indexes" component was created in the
> "database" product scope, then it should
> be available only there. Note however that a component with the same name
> can still be created in another
> product.
> Additionally, when you create a new product it is populated with the
> default components, milestones etc.,
> so each newly created product gets the same set of initial values.
>
> >
> > Or am I not understanding the intended use of those categories?
>
> Your understanding is correct, but from the questions above I'm assuming
> you're experiencing some issues
> with multiproduct. Could you describe the problem in more detail and if
> possible provide the steps to
> reproduce it? Thanks.
>
> >
> > -Tim
>
> --
> matevz
>
>
Re: multi-product components?
Posted by Matevž Bradač <ma...@digiverse.si>.
On 4. Jun, 2013, at 20:04, Tim Tisdall wrote:
> I see how to enter different products and I see how to enter components. However, shouldn't the components be dependent on a particular product?
Indeed they should be.
>
> For example, if I have products such as "database" and "game" and components "joystick control" and "btree indexes". When I create a ticket for the "game" product I don't think I should be able to select "btree indexes".
You are correct - if the "btree indexes" component was created in the "database" product scope, then it should
be available only there. Note however that a component with the same name can still be created in another
product.
Additionally, when you create a new product it is populated with the default components, milestones etc.,
so each newly created product gets the same set of initial values.
>
> Or am I not understanding the intended use of those categories?
Your understanding is correct, but from the questions above I'm assuming you're experiencing some issues
with multiproduct. Could you describe the problem in more detail and if possible provide the steps to
reproduce it? Thanks.
>
> -Tim
--
matevz