[Apache Bloodhound] Proposals/BEP-0008 modified
Page Proposals/BEP-0008 was changed by huaxiang Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diffversion=6 Revision 6 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 5) +++ Proposals/BEP-0008 (version: 6) @@ -32,6 +32,15 @@ Proposed solution: · Take snaps to keep the changes of statuses and the time those occurred. · Use data mining tools to find some patterns, generate time series reports. + + == Implementation +* Generate no-graphic time series reports: + This function could be simply added into existing reports page. Basically, columns from ticket and ticket_change tables would be retrieved. The 'time' column from ticket_change table is the time point when tickets changes occurred. + In order to provide correct time format, a new field named 'tctime' added into trac\trac\ticket\api.py. Relevant files were updated as well. + Devs also suggested the code would be structured in a plugin. + +* Generate graphic time series reports: + One option is using js. == Progress * Spot methods/functions can be used to generate time-series report. (Done by early July) ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008 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-0008' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0008 modified
Page Proposals/BEP-0008 was changed by huaxiang Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diffversion=8 Revision 8 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 7) +++ Proposals/BEP-0008 (version: 8) @@ -37,9 +37,9 @@ == Implementation #implementation * Generate no-graphic time series reports: - This function could be simply added into existing reports page. Basically, columns from ticket and ticket_change tables would be retrieved. The 'time' column from ticket_change table is the time point when tickets changes occurred. + At the first stage, this function could be simply added into existing reports page. Basically, columns from ticket and ticket_change tables would be retrieved. The 'time' column from ticket_change table records the time points when tickets changes occurred. In order to provide correct time format, a new field named 'tctime' added into trac\trac\ticket\api.py. Relevant files were updated as well. - Devs also suggested the code would be structured in a plugin. + Devs also suggested the code would be structured in a plugin rather than integrated into bloodhound. * Generate graphic time series reports: One option is using js. ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008 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-0008' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0008 modified
Page Proposals/BEP-0008 was changed by huaxiang Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diffversion=5 Revision 5 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 4) +++ Proposals/BEP-0008 (version: 5) @@ -29,15 +29,16 @@ To help the Bloodhound developers find the hidden information easily and make correct decisions. For example, for a particular type of tickets, the longer the time of changing status from 'assigned' to 'closed', the higher the difficulty level of solving. Therefore, the developers can allocate more resources for such type of tickets. -To help users to track the process of their own tickets, e.g., a message/email sent to the user once the status of the ticket was changed. - -To help developers and users get better understanding of the reports and make decisions. - Proposed solution: · Take snaps to keep the changes of statuses and the time those occurred. · Use data mining tools to find some patterns, generate time series reports. - == Rationale #rationale + == Progress +* Spot methods/functions can be used to generate time-series report. (Done by early July) +* Create non-graphic time-series reports for a specific query from local host. (Done by mid-term ) +* Add enhanced reports functionality. +* Generate graphic time-series reports. + == Implementation #implementation ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008 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-0008' page. If it was not you, please report to .
[Apache Bloodhound] Proposals/BEP-0008 modified
Page Proposals/BEP-0008 was changed by huaxiang Diff URL: https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008?action=diffversion=2 Revision 2 Changes: ---8--8--8--8--8--8--8--8 Index: Proposals/BEP-0008 = --- Proposals/BEP-0008 (version: 1) +++ Proposals/BEP-0008 (version: 2) @@ -1,85 +1,64 @@ -placeholder for Hua's proposal- -= BEP BEP number : BEP title #overview += BEP-0008 : Add time series reports #overview [[PageOutline]] -|| '''BEP''' || BEP number || -|| '''Title''' || BEP title || -|| '''Version''' || leave blank || -|| '''Last-Modified''' || leave blank || -|| '''Author''' || Author With Email u...@dom.ain, Author Name Only, or The Bloodhound project (see [wiki:/Proposals#bep-header-preamble BEP preamble explained]) || +|| '''BEP''' || BEP-0008 || +|| '''Title''' || Add time series reports || +|| '''Version''' || || +|| '''Last-Modified''' || || +|| '''Author''' || Hua Xiang huaxiang2...@gmail.com || || '''Status''' || Draft || -|| '''Type''' || BEP type (see [wiki:/Proposals#bep-types BEP types explained]) || +|| '''Type''' || || || '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] || -|| '''Created''' || leave blank || -|| '''Post-History''' || leave blank || +|| '''Created''' || || +|| '''Post-History''' || || == Abstract #abstract +In many organisations reports are tracking changes over time or and/or are prepared in a regular interval to capture information at a fixed point in time. The current reports functionality of Bloodhound doesn't serve these cases very well at the moment. Users also can't query information as it was at a given date. For solving this problem, the changes over time must be recorded. Data mining tools should also be involved in order to provide some patterns, generate time series reports, help user get better understanding of the reports and make decisions. -Delete text in this section and add a short (~200 word) description of the technical issue being addressed. Take a look at sample abstract below - -This template provides a boilerplate or sample template for creating your -own BEPs. In conjunction with the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] -, this should make it easy for you to conform your own -BEPs to the format outlined below. See [#howto How to Use This Template] for further instructions. - -**Note**: if you are reading this template via the web, you should first try to create a new wiki page by selecting `ProposalsRst` |page template guide|. **DO NOT EDIT THIS WIKI PAGE IN ORDER TO CREATE A NEW BEP! ** - -If you would prefer not to use WikiFormatting markup in your BEP, please see [wiki:/Proposals/Formats/RestructuredText reStructuredText BEP guidelines]. == Motivation == -The motivation is critical for BEPs that want to change the copy of ''Trac'' patched using vendor branch . It should clearly explain why the existing ''Bloodhound'' solution is inadequate to address the problem that the ''BEP'' solves. ''BEP'' submissions without sufficient motivation may be rejected outright. +The current “Reports” tool of bloodhound can provide a list based on custom queries (https://issues.apache.org/bloodhound/report). The historical statuses of tickets and the time point of such information, however, cannot be illustrated. These data are helpful for user to determine the hottest topics, allocate resources, evaluate performance etc. + == Proposal #proposal -The technical specification should describe any new features , detail its impact on the components architecture , mention what plugins will be included as a result , whether they are hosted by [http://trac-hacks.org trac-hacks.org] or not , and any other relevant technical subject . The specification should be detailed enough to allow competing, interoperable implementations for any of the current supported database platforms (e.g. ''SQLite'', ''Postgres'', ''MySQL'') and server technologies (e.g. ''Apache HTTPD server'', ''nginx'', ''mod_wsgi'', ''CGI'').. +To help the Bloodhound developers find the hidden information easily and make correct decisions. For example, for a particular type of tickets, the longer the time of changing status from 'assigned' to 'closed', the higher the difficulty level of solving. Therefore, the developers can allocate more resources for such type of tickets. -== Rationale #rationale +To help users to track the process of their own tickets, e.g., a message/email sent to the user once the status of the ticket was changed. -The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other issue
