#112: Implement mapping of resources to products
--------------------------+--------------------
Reporter: olemis | Owner: nobody
Type: task | Status: new
Priority: major | Milestone:
Component: multiproduct | Version:
Keywords: |
--------------------------+--------------------
AFAICS , this ticket comes in some steps .
1. Refine current resource mapping model (i.e.
`multiproduct.model.ProductResourceMap` class) .
This might also include implementing
[http://trac.edgewall.org/wiki/TracDev/Proposals/TracRelations
generic resource mapping proposal]
(e.g. milestone to version ...) rather than limiting the solution to
''product <--> resource'' use cases.
2. Upgrade web UI (e.g. admin panels , milestone view , ... ) in order
to
introduce input controls in forms allowing to select target products
3. Decide which models should be considered for resource management
(e.g. `trac.resource.IResourceManager`) and implement it if missing .
4. Upgrade resource API by including classifiers/tags (e.g. ticket
keywords,
[http://trac.edgewall.org/wiki/TracDev/Proposals/ProjectLabels
product labels], ...)
Examples of ''resources'' to map should be tickets (<= currently using
ticket field ) , versions , milestones , components , wiki pages ,
repositories (<= or individual changesets, branches ... )
'''PS''' : This seems to be a huge amount of work , so maybe it'll be
better to start with this ticket and create other for each part mentioned
above , or simpler tasks needed to achieve each goal .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/112>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
