You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Jure Zitnik <ju...@digiverse.si> on 2012/11/14 16:19:19 UTC
Re: [Apache Bloodhound] Proposals/BEP-0003 modified
Hi all,
I added a rough list of proposed features for multi product support to
BEP-0003 wiki. Please review and comment.
I would suggest that we start discussions on each of the proposed
features on bloodhound-dev@, mail subject on proposed features should be
in the form of '[BEP-0003] <feature name>' (according to BEP Guideliness).
Cheers,
Jure
On 11/14/12 4:13 PM, Apache Bloodhound wrote:
> Page "Proposals/BEP-0003" was changed by jure
> Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=5>
> Revision 5
> Comment: Initial feature list proposal
> Changes:
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
> Index: Proposals/BEP-0003
> =========================================================================
> --- Proposals/BEP-0003 (version: 4)
> +++ Proposals/BEP-0003 (version: 5)
> @@ -30,7 +30,37 @@
>
> == Proposal #proposal
>
> -'''TODO'''
> +The following is a list of proposed features for multi product support in Bloodhound.
> +
> +=== Product/ticket namespaces
> +Product and ticket ID should form a two dimensional namespace, tickets would in addition to current URL scheme also be addressable through the product URL namespace, namely /ticket/<product>/<id>. Each product would have a separate numberspace for product ticket IDs.
> +
> +=== Tickets moveable between products
> +Tickets should be moveable between products, old ticket product IDs (and URLs) should be remembered, making the same ticket accessible through old products namespaces (URLs).
> +
> +=== Per product search
> +By default, search is global. Search and queries should allow search queries to be limited to specific product.
> +
> +=== Per product ticket workflow
> +Depending on the product, different ticket workflows should be supported.
> +
> +=== Inter product ticket relations
> +It should be possible to link tickets from different products.
> +
> +=== Per product notifications
> +Notifications should be configurable per product.
> +
> +=== Per product ticket field configuration
> +Components, milestone, version, priority, defaults, custom fields should be configurable per product.
> +
> +=== Product roles
> +Support for per product user groups. Roles can be used to configure notifications and permissions per product.
> +
> +=== Per product permission scheme
> +Permission scheme is defined by assigning permissions (from a predefined permission list) to specific users or groups. Permission scheme is assigned to a product.
> +
> +=== Per product repository
> +Each product can have different repository (and type) assigned.
>
> == Rationale #rationale
>
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>
> --
> Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound (incubating) issue tracker
>
> This is an automated message. Someone added your email address to be
> notified of changes on 'Proposals/BEP-0003' page.
> If it was not you, please report to .
Re: [Apache Bloodhound] Proposals/BEP-0003 modified
Posted by Olemis Lang <ol...@gmail.com>.
I'll follow soon ;)
Thanks !
On 11/14/12, Jure Zitnik <ju...@digiverse.si> wrote:
> Hi all,
>
> I added a rough list of proposed features for multi product support to
> BEP-0003 wiki. Please review and comment.
>
> I would suggest that we start discussions on each of the proposed
> features on bloodhound-dev@, mail subject on proposed features should be
> in the form of '[BEP-0003] <feature name>' (according to BEP Guideliness).
>
> Cheers,
> Jure
>
> On 11/14/12 4:13 PM, Apache Bloodhound wrote:
>> Page "Proposals/BEP-0003" was changed by jure
>> Diff URL:
>> <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=5>
>> Revision 5
>> Comment: Initial feature list proposal
>> Changes:
>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>> Index: Proposals/BEP-0003
>> =========================================================================
>> --- Proposals/BEP-0003 (version: 4)
>> +++ Proposals/BEP-0003 (version: 5)
>> @@ -30,7 +30,37 @@
>>
>> == Proposal #proposal
>>
>> -'''TODO'''
>> +The following is a list of proposed features for multi product support in
>> Bloodhound.
>> +
>> +=== Product/ticket namespaces
>> +Product and ticket ID should form a two dimensional namespace, tickets
>> would in addition to current URL scheme also be addressable through the
>> product URL namespace, namely /ticket/<product>/<id>. Each product would
>> have a separate numberspace for product ticket IDs.
>> +
>> +=== Tickets moveable between products
>> +Tickets should be moveable between products, old ticket product IDs (and
>> URLs) should be remembered, making the same ticket accessible through old
>> products namespaces (URLs).
>> +
>> +=== Per product search
>> +By default, search is global. Search and queries should allow search
>> queries to be limited to specific product.
>> +
>> +=== Per product ticket workflow
>> +Depending on the product, different ticket workflows should be
>> supported.
>> +
>> +=== Inter product ticket relations
>> +It should be possible to link tickets from different products.
>> +
>> +=== Per product notifications
>> +Notifications should be configurable per product.
>> +
>> +=== Per product ticket field configuration
>> +Components, milestone, version, priority, defaults, custom fields should
>> be configurable per product.
>> +
>> +=== Product roles
>> +Support for per product user groups. Roles can be used to configure
>> notifications and permissions per product.
>> +
>> +=== Per product permission scheme
>> +Permission scheme is defined by assigning permissions (from a predefined
>> permission list) to specific users or groups. Permission scheme is
>> assigned to a product.
>> +
>> +=== Per product repository
>> +Each product can have different repository (and type) assigned.
>>
>> == Rationale #rationale
>>
>> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>>
>> --
>> Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003>
>> Apache Bloodhound <https://issues.apache.org/bloodhound/>
>> The Apache Bloodhound (incubating) issue tracker
>>
>> This is an automated message. Someone added your email address to be
>> notified of changes on 'Proposals/BEP-0003' page.
>> If it was not you, please report to .
>
>
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
[BEP-0003] Product/ticket namespaces (Was: Re: [Apache Bloodhound]
Proposals/BEP-0003 modified)
Posted by Gary Martin <ga...@wandisco.com>.
On 14/11/12 15:19, Jure Zitnik wrote:
> Hi all,
>
> I added a rough list of proposed features for multi product support to
> BEP-0003 wiki. Please review and comment.
>
> I would suggest that we start discussions on each of the proposed
> features on bloodhound-dev@, mail subject on proposed features should
> be in the form of '[BEP-0003] <feature name>' (according to BEP
> Guideliness).
Heh.. I see I missed a few decisions on how we would be doing all this.
Oh well.
>
>> +=== Product/ticket namespaces
>> +Product and ticket ID should form a two dimensional namespace,
>> tickets would in addition to current URL scheme also be addressable
>> through the product URL namespace, namely /ticket/<product>/<id>.
>> Each product would have a separate numberspace for product ticket IDs.
>> +
I would probably go with a more general
/<product>/<resource-name>/<resource-id> scheme - as in /bh/ticket/1234.
To increase the potential namespace for this scheme, paths would
probably have to be preceded by something to identify it as a product
prefix as well though.
Cheers,
Gary