= Tickets for project tasks =

== Description ==

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 developper 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.

This is just a first try (im new to python and trac development), with might 
be extended in future.

BEWARE: This version assumes you have a custom field {{{project}}} which takes project names (dropdown in our case).

== Bugs/Feature Requests == 

Existing bugs and feature requests for TaskTicketsMacro are 
[report:9?COMPONENT=TaskTicketsMacro here].

If you have any issues, create a 
[http://trac-hacks.org/newticket?component=TaskTicketsMacro&owner=viola new ticket].

== Download, Source ==

Download the zipped source from [download:taskticketsmacro here], check out TaskTicketsMacro from the [http://trac-hacks.org/svn/taskticketsmacro Subversion repository], or [source:taskticketsmacro browse the source] with Trac.

== Installation, Example ==



{{{SCREENSHOT}}}

easyinstall is not yet provided.

Simply copy the three Python-Scripts to your plugin Directoy and restart.


In the header, enter field values for preselecting fields in newticket.
In 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]]
}}}

== Recent Changes ==

[[ChangeLog(taskticketsmacro, 3)]]

== Author/Contributors ==

'''Author:''' [wiki:viola] [[BR]]
'''Contributors:'''