Changes between Version 2 and Version 3 of SubticketsPlugin/Reporting
- Timestamp:
- Dec 15, 2016, 8:19:50 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SubticketsPlugin/Reporting
v2 v3 1 1 [[TOC]] 2 2 3 The plugin contains stored functions that can aid reporting of subticket hierarchies. Using such functions is necessary due to TracReports rewriting of SQL queries. 3 = Reporting subtickets for Trac 4 4 5 The functions are found in the `reporting` [https://github.com/trac-hacks/trac-subtickets-plugin/tree/master/tracsubtickets/reportings subdirectory of the plugin code] 5 The plugin SubticketsPlugin contains stored functions that can aid in the reporting of subticket hierarchies in Trac. Using such functions is necessary due to TracReports rewriting of SQL queries. 6 7 The functions are found in the `reporting` [https://github.com/trac-hacks/trac-subtickets-plugin/tree/master/tracsubtickets/reportings subdirectory of the plugin code]. 6 8 7 9 Currently only PostgreSQL is supported. The query technique used is supported by at least MySql and SQLServer, but the DDLs differ slightly. Patches are welcome. 8 10 9 == Simple Example ==11 == Simple Example 10 12 11 13 The `tracsubticket_tree()` function returns a depth-first search of all tickets and subtickets. A simple report using that function is: … … 25 27 }}} 26 28 27 The result of this report query looks like this:29 The result of this report query looks as follows: 28 30 29 [[Image(tracsubtickets_simple_report )]]31 [[Image(tracsubtickets_simple_report, border=2)]] 30 32 31 33 Thanks to [https://schneimi.wordpress.com/2013/02/02/trac-subticketsplugin-with-progress-bar-and-report/ schneimi] for the idea.