Changes between Version 34 and Version 35 of TimeVisualizerPlugin


Ignore:
Timestamp:
May 25, 2020, 10:09:39 PM (4 years ago)
Author:
figaro
Comment:

RFemove non-standard and duplicated links.

Legend:

Unmodified
Added
Removed
Modified

  • TimeVisualizerPlugin

    v34 v35  
    22
    33= Render burndown images in svg format
    4 
    5 '''Links:'''
    6 [query:status!=closed&component=TimeVisualizerPlugin&order=priority open tickets]
    7 | [/newticket?component=TimeVisualizerPlugin new ticket]
    8 | [/svn/timevisualizerplugin svn]
    9 | [browser:timevisualizerplugin browse code]
    104
    115== Description
    … …  
    137This plugin creates customizable burndown graphs from the ticket history provided by TimingAndEstimationPlugin. Dynamic graphs can be easily embedded into Trac wiki pages.
    148
    15 To test graphs and filtering, access yopur project environment, such as the following: `http://server:port/path/to/trac/env/tractimevisualizer`. It will render the hours from the whole project's life cycle.
     9To test graphs and filtering, access your project environment, such as the following: `http://server:port/path/to/trac/env/tractimevisualizer`. It will render the hours from the whole project's life cycle and display the graph in svg format.
    1610
    17 More practical is to get graphs from 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.
     11More practical is to get graphs from a certain time frame and filter the hours based on milestone and/or component. This is achieved with macro !BurnDown. This plugin replaces ScrumBurndownPlugin, because its graphing capabilities are limited and it modifies the database schema.
    1812
    1913In my example project, I have a wiki page with following content: