As 3.1 winds down and early 3.2 developm…

As 3.1 winds down and early 3.2 development is likely to start soon, I’m trying to make TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. a bit more usable, ranging from reports to the theme itself.

I’ve been tinkering with report 40, Tickets Awaiting Review. It now uses the type of ticketticket Created for both bug reports and feature development on the bug tracker., version it was reported against, and keywords, to create five groups of tickets:

  • Defects Awaiting Review, reported against trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. (or no version number specified)
  • Defects Awaiting Review, reported against latest branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".
  • Defects Awaiting Review (all other bugs)
  • Enhancements Awaiting Review (includes feature requests)
  • Reporter Feedback / Close (tickets marked for reporter-feedback or close, which overrides the other groups)

Each group is then sorted in descending order from when the ticket was last modified. Right now the first two groups are the same, but I’ll modify the report once 3.2 development starts.

Ideally, this will allow us to better track and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. incoming tickets. It also increases the significance of the ‘Version’ field (version it was reported against, but ideally earliest version to which the ticket applies) and removing reporter-feedback when feedback is provided.

I’ll be working on report 39 (Candidates for 3.2) soon. Suggestions welcome for improvements on both.