Hi all,
I was looking into enhancing multi product support within Bloodhound.
afaik current multi product support consists of the ability to
define/administer product(s) and the ability to assign product to a
ticket. What I was thinking of starting with are the following rather
simple features/functionalities:
1. product/ticket namespaces - product and ticket ID would 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. The same might also be applied for wikis, not
sure about whether it's something that would come handy or not.
2. tickets should be moveable between products, old ticket product IDs
(and URLs) should be remembered, making the same ticket accessible
through old products namespaces.
3. enhance query to limit the search to specific product
Down the line it'd be really useful to have per product permissions,
versions, milestones, components, ticket lifecycles, predefined queries,
etc., which is a bit more complex part that should be discussed in a
separate thread.
Any comments/suggestions on this?
Cheers,
Jure