Notice: This plugin is unmaintained and availableforadoption.
We tried to use Trac for planning small projects.Tasks should be tickets. Entering tasks should be simple. Really simple.On the project page you should have the status overview.Each developer should then have her task list.
We created three simple macros for generating a tabular project task outline.Initially, task summaries are linked to the newticket form, all appropriate fields filled out. After having created the task ticket, summary is linked to the ticket itself.
Note: The macro is currently in German. The table generated has the header names: Entwickler, Datum, Aufgabe, Aufwand, which in English translates to: Owner, Due Date, Task, Effort. You may easily change this in TicketHeader.py.
Note: This version assumes you have a custom fieldproject, which takes project names (dropdown in our case).
Existing bugs and feature requests forTaskTicketsMacro arehere.
If you have any issues, create anew ticket.
| defect | 0 / 2 | ||
|---|---|---|---|
| enhancement | 2 / 2 |
Download the zipped source fromhere.
Check outTaskTicketsMacro from theSubversion repository, orbrowse the source with Trac.
Placeholder for screenshot
easyinstall is not yet provided.
Simply copy the 3 Python-Scripts to your plugin directory and restart:
trac-admin /instance_trac/ upgrade
In the headerheader of what?, enter field values for preselecting the fields owner and project in newticket.Please turn this sentence into 3 or 4 sentences and define termsIn the ticket, enter due date, summary and effort.In the footer, efforts are summed up.
[[TicketHeader(heyduk||FlowOpt1)]][[Ticket(24.01.2008 ||HeartBeat-Analyse, Loganalyse, DB-Indizes|| 1.75)]]...[[TicketFooter]]
Author:viola
Maintainer:none (needsadoption)
Contributors:
