You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/12/12 15:49:56 UTC

[Apache Bloodhound] Proposals/BEP-0003 modified

Page "Proposals/BEP-0003" was changed by jure
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003?action=diff&version=22>
Revision 22
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0003
=========================================================================
--- Proposals/BEP-0003 (version: 21)
+++ Proposals/BEP-0003 (version: 22)
@@ -155,16 +155,18 @@
 
 Currently, products are only supported in relation to tickets. Current implementation of `bloodhound_multiproduct` plugin extends the `ticket` table by adding custom field `product`. This field is used to reference products as defined in the `bloodhound_product` table.
 
-In addition to tickets, other entities should also be made ''product aware''. The product support should be, in a similar way to tickets, extended to (at least) the following database entities within ''Bloodhound'':
-* versions
-* milestones
-* components
-* priorities
-* ...
-
-This could be accomplished using the same approach as used in relation to tickets - by extending the database tables with the 'product' field that would reference the product that the specified entities belong to.
+In addition to tickets, other entities should also be made ''product aware''. The product support will be added to the following database tables within ''Bloodhound'':
+||= Table =||= Current key =||= New key =||
+|| enum || type, name || type, name, product ||
+|| component || name || name, product ||
+|| milestone || name || name, product ||
+|| version || name || name, product ||
+|| wiki || name, version || name, version, product ||
+
+This will be accomplished using the same approach as used in relation to tickets - by extending the database tables with the 'product' field that would reference the product that the specified entities belong to.
 
 Another change required is the change of the fore mentioned table keys. As it currently stands, the key used in these tables is limited to the 'name' field. As this (in the modified schema) prevents users from creating versions/milestones/... with the same name for different products, key should be extended with the 'product' field.
+
 
 === Administration commands #admin-cmd
 
-------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 .