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 <de...@bloodhound.apache.org> on 2013/07/28 21:07:23 UTC

[Apache Bloodhound] Proposals/BEP-0007 modified

Page "Proposals/BEP-0007" was changed by antonia.horincar
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007?action=diff&version=4>
Revision 4
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0007
=========================================================================
--- Proposals/BEP-0007 (version: 3)
+++ Proposals/BEP-0007 (version: 4)
@@ -37,8 +37,44 @@
 
 The back end side of the project will consist of building a REST API for interacting with the objects from external sources. The IRequestHandler interface will be extended by a class that will match, process and deal with the information retrieved. Several other interfaces, such as IPermissionRequestor (for checking what the permissions for a specific ticket/object are) and ITemplateProvider might need to be extended as well. 
 
-Ideally the system could display any arbitrary Bloodhound widgets, so some of the previous code used for developing Bloodhound widgets can be reused. The Bloodhound widgets can currently be displayed by their name (e.g. !TicketQuery, !WidgetDoc, etc.), and some possible parameters (e.g. query=”status=opened”). The solution described above can be extended to be more generic. All kinds of widgets could be embedded using iframe tags presented in the previous paragraphs.
+Tickets, milestones, products and queries are some of the objects that could be embedded on external services. The following information should be displayed when embedding these objects:
 
+'''Tickets:'''
+- ID
+- Summary 
+- Owner
+- Reporter
+- Keywords
+- Type
+- Status
+- Priority
+- Milestone
+- Component
+- Version
+- Severity
+- Number of comments
+- Number of attachments
+
+'''Milestones:'''
+- Name
+- Status (completed, late or due date)
+- Description
+- Product 
+- Number of tickets
+- Number of attachments
+
+'''Products:'''
+- Name
+- Description
+- Owner
+- Number of tickets
+- Number of milestones
+- Number of versions
+- Number of components
+
+'''Queries:'''
+- Query details (the fields used when creating the query)
+- Results
 
 
 == Rationale #rationale
@@ -58,6 +94,8 @@
 
 [[Widget(TicketQuery, query="keywords=~bep-0007&col=id&col=summary&col=status&col=priority&col=milestone", title=BEP 7 ticket summary)]]
 
+'''Current state of the implementation:'''
+At this point the API can retrieve information about tickets, milestones and products. It can also retrieve information about queries, but not for all the cases (there are some cases when the API fails to correctly retrieve query results, therefore this part is still being worked on).
 
 == Resources #resources
 
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0007>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker

This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0007' page.
If it was not you, please report to .