Multiple ticket creation from one page

[jwm@…]

In order to aid in the creation of Joel On Software style schedules it's necessary to break down big tasks into a lot of smaller tasks that will take a more predictable time. Easy to do in a spread sheet, but a nuisance to do via the standard new ticket → fill out a form → submit cycle. In fact, this is grueling to the point of giving up when you're on one side of a 128k connection, and the server is on the other side of it's own 128k connection.

I crave this (and may other client side optimisations) so much I'm willing to code them myself, but I thought I'd check with the main development team to see what work is already in progress first, before marching ahead.

[Christian Boos]

See also #2193.

But you suggested a different way to create subtickets: IIUC, you want to have the possibility to create from a parent ticket many children ticket at once.

What user interface would you suggest for that?

[anonymous]

I am primarily interested in cutting down on the server round trips, or at least, the user experience of UI latency that usually results. So the interface I'm interested in should handle the general business of creating tickets, while being subticket aware, in some sense.

The kind of interface I'm thinking of would condense a ticket submission into a "row", probably two or three lines deep. A "more tickets" button would insert more rows to fill out.

Two aspects are hard problems. One is whether to handle long descriptions, and how to make that happen, the other is how to handle subtickets, and therefore, reparenting. A bit of experimentation will be required, I expect :-)

[chicks]

I'd be interested in this feature as well. Even if it was available via the trac-admin console. Right now, I'm adding rows to the sql tables manually.

[Markus Tacker <m@…>]

You could use email to create tickets. See the, now updated ​EmailtoTracScript.

[Christian Boos]

I don't see this being done in Trac core, however it should be quite possible to create a plugin for this.

See also #4686 (ticket cloning).