Trac Feature Requests and Discussion

This is the proper place, outside the MailingList, to propose features, functionality ideas and discuss things you would like to see in future versions of Trac.

Please also consider ​submitting a feature request.

See also: TracTickets, WildIdeas

Suggestions

• User Session Breadcrumbs above wiki pages that reveal pages the visitor has clicked through.
• Enable Trac to operate remote from the SVN repository (ie. over the ​http:// and/or ​svn:// protocols)
• Drop down menu for view tickets to go directly to the right report
• Answer by email to email notification gets stored as a comment, attached files as well (see roundup issue tracker ​http://roundup.sourceforge.net)
• Ability to subscribe for email notification of changes to a specific wiki page.
• Tickets should get 'time planned' and 'time spent on ticket' fields, in man hours. Those values should be consulted for a milestone's progress bar. That feature would enable users to use the ticket/milestone system for planning development processes.
• Allow users to switch between wiki markup edit mode and a wysiwyg editor such as fckeditor ala seedwiki (​http://www.seedwiki.com/wiki/online_teaching_and_learning_issues/online_teaching_and_learning_issues.cfm?wpid=&edit=yes&editorchoice=3)
• Add additional fields to ticket: steps to reproduce, expected results, observed results (see (​http://www.joelonsoftware.com/articles/fog0000000029.html)) (one comment: These could just go in additional comments, no more fields please.)
• Clarify the Trac ticket system for use as a TODO checklist, instead of a "bug tracker." eg, "normal" severity is currently used for TODO items.

• provide closed tickets by milestone RELEASE file (xml or otherwise