Trac improvements!

A number of tweaks to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. have just been pushed live, restoring our Trac template broken a few months ago and adding a number of new enhancements.

The biggest change is a new workflow for keywords. (Believe it or not, the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. is mine.) It is now a nifty tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) list with a drop-down:

I tried to order them in a way that makes sense. Recognized keywords also have tooltips explaining what they mean. As a last resort, you can still manually edit keywords by clicking the little link. Also, a few keywords will be hidden for most users.

Other changes:

• There’s now a giant warning when creating a ticketticket Created for both bug reports and feature development on the bug tracker.. (Embedded at right.) Most of the text is from our old template, and the visual was inspired by jQuery’s warning.
• Tickets are again left-aligned. The ticket properties and attachments should also now be easier to scan. The Modify section is now open by default again.
• Gravatars are back for comments, and were added to reporters and owners.
• The After the Deadline button is back, and integrated nicely into the toolbar. (You can see this in either screenshot.)
• Long ticket titles no longer force horizontal scrolling on reports.
• There is now a license note when uploading a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..

Please suggest any other Trac improvements, and find me if there are any bugs.