Changes between Version 61 and Version 62 of TracFormsPlugin


Ignore:
Timestamp:
Nov 30, 2010, 2:25:29 PM (4 years ago)
Author:
hasienda
Comment:

link changed from report to query showing more ticket details now

Legend:

Unmodified
Added
Removed
Modified
  • TracFormsPlugin

    v61 v62  
    5858}}}
    5959
    60 Note that the form is blank and you can play with the results again.  This is because the default context for the form is the page URL itself!  That means that as long as a form is included on a different page (and the default context is not overridden), then each page including gets its '''own''' version of the form's results.  This works particularly well with PageTemplates.
     60Note that the form is blank and you can play with the results again.  This is because the default context for the form is the page URL itself!  That means that as long as a form is included on a different page (and the default context is not overridden), then each page including gets its '''own''' version of the form's results.  This works particularly well with !PageTemplates.
    6161
    6262Now, for more fun, do the same thing in a ticket.  Once submitted, every ticket including the template will contain it's own checklist.  One obvious use for this is when creating a svn commit checklist.  Simply put the checklist in the appropriate wiki location, create tickets that include the location, and voila, instant commit step-by-step.  Once enough of the form becomes exposed, we should be able to work this into the workflow too (no resolving before at least paying lip service to the checklist).
     
    6767
    6868Existing bugs and feature requests for TracFormsPlugin are
    69 [report:9?COMPONENT=TracFormsPlugin here].
     69[query:status=new&status=assigned&status=!closed&component=TracFormsPlugin&order=priority here].
    7070
    7171If you have any issues, create a