| 1 | = Tickets for project tasks = |
| 2 | |
| 3 | == Description == |
| 4 | |
| 5 | We tried to use trac for planning small projects. |
| 6 | Tasks should be tickets. Entering tasks should be simple. Really simple. |
| 7 | On the project page you should have the status overview. |
| 8 | Each developper should then have her task list. |
| 9 | |
| 10 | We created three simple macros for generating a tabular project task outline. |
| 11 | Initially, task summaries are linked to the newticket form, all appropriate fields filled out. After having created the task ticket, summary is linked to |
| 12 | the ticket itself. |
| 13 | |
| 14 | This is just a first try (im new to python and trac developpment), with might |
| 15 | be extended in future. |
| 16 | |
| 17 | == Bugs/Feature Requests == |
| 18 | |
| 19 | Existing bugs and feature requests for TaskTicketsMacro are |
| 20 | [report:9?COMPONENT=TaskTicketsMacro here]. |
| 21 | |
| 22 | If you have any issues, create a |
| 23 | [http://trac-hacks.org/newticket?component=TaskTicketsMacro&owner=viola new ticket]. |
| 24 | |
| 25 | == Download == |
| 26 | |
| 27 | Download the zipped source from [download:taskticketsmacro here]. |
| 28 | |
| 29 | == Source == |
| 30 | |
| 31 | You can check out TaskTicketsMacro from [http://trac-hacks.org/svn/taskticketsmacro here] using Subversion, or [source:taskticketsmacro browse the source] with Trac. |
| 32 | |
| 33 | == Example == |
| 34 | |
| 35 | In the header, enter field values for preselecting fields in newticket. |
| 36 | In the ticket, enter due date, summary and effort. |
| 37 | In the footer, efforts are summed up. |
| 38 | {{{ |
| 39 | [[TicketHeader(heyduk||FlowOpt1)]] |
| 40 | [[Ticket(24.01.2008 ||HeartBeat-Analyse, Loganalyse, DB-Indizes|| 1.75)]] |
| 41 | ... |
| 42 | [[TicketFooter]] |
| 43 | }}} |
| 44 | |
| 45 | == Recent Changes == |
| 46 | |
| 47 | [[ChangeLog(taskticketsmacro, 3)]] |
| 48 | |
| 49 | == Author/Contributors == |
| 50 | |
| 51 | '''Author:''' [wiki:viola] [[BR]] |
| 52 | '''Contributors:''' |