Changes between Version 30 and Version 31 of TimeVisualizerPlugin
- Timestamp:
- Jan 18, 2016, 5:29:30 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TimeVisualizerPlugin
v30 v31 1 1 [[PageOutline(2-5,Contents,pullout)]] 2 2 3 = Plugin to render burndown SVG images3 = Render burndown images in svg format 4 4 5 5 '''Links:''' 6 [query:status!=closed&component=TimeVisualizerPlugin&order=priority open #]7 | [ http://trac-hacks.org/newticket?component=TimeVisualizerPlugin&owner=mape new #]6 [query:status!=closed&component=TimeVisualizerPlugin&order=priority open tickets] 7 | [/newticket?component=TimeVisualizerPlugin new ticket] 8 8 | [/svn/timevisualizerplugin svn] 9 | [browser:timevisualizerplugin browse ]9 | [browser:timevisualizerplugin browse code] 10 10 11 11 == Description 12 12 13 This component draws customizable burndown graphs from ticket history provided by TimingAndEstimationPlugin. Dynamic graphs can be easily embedded towiki pages.13 This plugin creates customizable burndown graphs from the ticket history provided by TimingAndEstimationPlugin. Dynamic graphs can be easily embedded into Trac wiki pages. 14 14 15 15 Developed and tested with Trac 0.10.4, Python 2.4, sqlite, mod_python and Apache on Windows. The 0.6 version works on Trac 0.11. … … 17 17 == Bugs/Feature Requests 18 18 19 Existing bugs and feature requests for TimeVisualizerPlugin are [query:?status=new&status=assigned&status=reopened&group=&component=TimeVisualizerPlugin&order=priority here]. 19 Existing bugs and feature requests for TimeVisualizerPlugin are 20 [report:9?COMPONENT=TimeVisualizerPlugin here]. 20 21 21 If you have any issues, create a [/newticket?component=TimeVisualizerPlugin new ticket]. 22 If you have any issues, create a 23 [/newticket?component=TimeVisualizerPlugin new ticket]. 22 24 23 25 [[TicketQuery(component=TimeVisualizerPlugin,group=type,format=progress)]] … … 25 27 == Installation 26 28 27 '''Dependencies:''' TimingAndEstimationPlugin was needed in 0.4 and earlier versions to feed database with estimates and totalhours custom tickets. Browser must render SVG natively and support the html tag iframe. Latest Firefox, Opera and Safari browser versions should work.29 '''Dependencies:''' TimingAndEstimationPlugin was needed in 0.4 and earlier versions to feed the database with estimates and totalhours custom tickets. Browser must be able render SVG natively and support the html tag iframe. The latest Firefox, Opera and Safari browser versions should work. 28 30 29 1. Get source installation & install it30 {{{#!sh31 1. Get source files and install it: 32 {{{#!sh 31 33 svn co http://trac-hacks.org/svn/timevisualizerplugin/branches/TimeVisualizer_0.6 32 34 cd TimeVisualizer_0.6 33 35 python setup.py install 34 36 }}} 35 2. Edit your `trac.ini` file and modify components section:36 {{{#!ini37 1. Edit your `trac.ini` file to enable the plugin: 38 {{{#!ini 37 39 [components] 38 40 <...other components...> 39 41 tractimevisualizerplugin.* = enabled 40 42 }}} 41 3. Restart server to propagate changes.43 1. Restart server to propagate changes. 42 44 43 45 For details, see browser:/timevisualizerplugin/branches/TimeVisualizer_0.6/release_notes.txt … … 45 47 == Usage 46 48 47 To test graphs & filtering, access "http://server:port/path_to_trac_env/tractimevisualizer". It will render hours from whole projectlife cycle.49 To test graphs and filtering, access "http://server:port/path_to_trac_env/tractimevisualizer". It will render the hours from the whole project's life cycle. 48 50 49 More practical is to get graphs from some certain time frame and filter hours based on milestone and/or component. This is achieved with macro !BurnDown (wrote this plugin to replace ScrumBurndownPlugin because its graphing capabilities were limited and it modifies the database schema).51 More practical is to get graphs from some a certain time frame and filter the hours based on milestone and/or component. This is achieved with macro !BurnDown. I wrote this plugin to replace ScrumBurndownPlugin because its graphing capabilities were limited and it modifies the database schema. 50 52 51 In my example project, I have wiki page with following content:53 In my example project, I have a wiki page with following content: 52 54 {{{ 53 55 [[BurnDown(width=800,height=200,query=targetmilestone=mile1&datestart=08/8/07&dateend=8/22/07)]] … … 57 59 }}} 58 60 59 It renders the following graphs (picture is cropped to fit better on this page) 61 It renders the following graphs (picture is cropped to fit better on this page): 60 62 61 63 [[Image(TracTimeVisualizerPlugin_ss1.PNG)]] … … 67 69 == Feedback 68 70 69 [wiki:TimeVisualizerPlugin/FeedBack Feel free to give feedback] 71 Feel free to [wiki:TimeVisualizerPlugin/FeedBack give feedback]. 70 72 71 73 == Recent Changes 72 74 73 [[ChangeLog(timevisualizerplugin, 5)]]75 [[ChangeLog(timevisualizerplugin, 3)]] 74 76 75 77 == Author/Contributors