TODO's from Sourcecode as a ticket

[anonymous]

If you have in the Source Code:

  // TODO: Add Error Handling

This should generate a Ticket.

Maybe I write a patch for this…

[Emmanuel Blot]

I don't see this feature integrated in the core version.
Such a feature could be easily implemented as a Subversion hook script anyway.

[anonymous]

+1 from me. It would be sweet if the workflow went like this:

• TODO, FIXME, etc would create a task ticket and link to the source file as part of the ticket body, and assign the ticket to the person who commited the file
• When the source file is changed, if the TODO comment is no longer there the ticket is automatically closed

The ​CodeTagsPlugin will parse the source code and give you a list of items, but it would be killer to see the ticket system integrated with this type of thing.

[sid]

This does not seem like a core feature.

But that said, a starting point would be the trac-post-commit-hook script. This already updates tickets based on changeset comments. In this case, you could use the ​CodeTagsPlugin to create the code / changeset info list, and then create a new ticket for each of those items.

[Christian Boos]

It would be quite doable to add an processing step in the pygments HTML renderer, so that comments would be treated specially. Getting TODO references would be one thing, wiki formatting comments would be another.

[Christian Boos]

Milestone 1.0 deleted

[Christian Boos]

See also #1520.