Changes between Version 15 and Version 16 of ProgressMeterMacro


Ignore:
Timestamp:
Oct 31, 2008, 5:00:45 PM (15 years ago)
Author:
Andrej Tokarčík
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProgressMeterMacro

    v15 v16  
    55This macro plugin was created because of [http://code.google.com/p/google-highly-open-participation-psf/issues/detail?id=256 this task] for GHOP/Python Software Foundation.
    66
    7 It contains a macro to display progress meter similar to the meters visible in the Roadmap within a wiki page. The !ProgressMeter macro works with the same arguments as !TicketQuery macro (available in the standard Trac distribution) -- except 'status' argument logically. It can be used for example for building complete report of the progress on tickets owned by a particular person. Actually the macro just counts the tickets matching given criteria and shows the meter (closed-to-active-tickets ratio).
     7It contains a macro to display progress meter similar to the meters visible in the Roadmap within a wiki page. The !ProgressMeter macro works with the same arguments as !TicketQuery macro -- except 'status' argument logically (which is handled differently, see [#usage usage]). It can be used for example for building complete report of the progress on tickets owned by a particular person. Actually the macro just counts the tickets matching given criteria and shows the meter (closed-to-active-tickets ratio).
    88
    9 A longer description can be found at the mentioned web page of GHOP task.
     9A longer description is available at the mentioned web page of GHOP task.
    1010
    1111== Download ==
     
    1717You can check out ProgressMeterMacro from [http://trac-hacks.org/svn/progressmetermacro here] using Subversion, or [source:progressmetermacro browse the source] with Trac.
    1818
    19 == Usage examples ==
     19== Usage examples == #usage
    2020
    2121Displays progress meter on tickets owned by 'qwp0' within milestone '0.1a':
     
    2929}}}
    3030
    31 == Bugs/Feature Requests ==
     31Using the {{{status}}} arg you can define statuses which will be considered as closed, separated by '|'. The 'closed' status is not default -- you have to specify it explicitly if you want it to be inclosed with the other statuses. Also, at the moment you can't use this arg as the only one.
     32{{{
     33[[ProgressMeter(status=closed|ready for QA, owner=$USER)]]
     34}}}
     35
     36== Bugs/Feature Requests ==
    3237
    3338Existing bugs and feature requests for ProgressMeterMacro are [query:status!=closed&component=ProgressMeterMacro&order=priority here]. If you have any issues, create a [/newticket?component=ProgressMeterMacro&owner=qwp0 new ticket].