Available Reports

Compose a new ticket query by selecting filters and columns to display.

Show all opened tickets related to the version control modules:

• mercurial plugin
• git plugin
• version control
• version control/browser
• version control/changeset view
• version control/log view

This report demonstrates the use of the automatically set USER dynamic variable, replaced with the username of the logged in user when executed.

Only tickets not already closed, btw.

This report displays the active tickets that have not yet been assigned to a Milestone, ordered by last modified date.

Those are the tickets that have not yet been analyzed by the TracTeam and are meant to be triaged.

Notes:

• the untriaged tickets for which a request for more information has been made (needinfo keyword) have been excluded from this report.
  See {21} for all needinfo tickets.
• the Chgs_Auths field corresponds to: (number of changes) by (number of different change authors), and can be used as an indicator of the popularity of the issue

This report displays the active tickets that have the "needinfo" keyword, ordered by last modified date.

This complements the {20} report, which doesn't contain the needinfo tickets anymore.

As a rule of thumb, unanswered tickets over 3 months old can be closed as worksforme or wontfix (see TracTicketTriage#StatusandResolution for the details).

Those are the tickets for the next Trac release, 1.2, 1.2.1, 1.2.2, etc.

Notes:

• the needinfo tickets have been excluded from this report (see {21}).
• the Chgs_Auths field corresponds to: (number of changes) by (number of different change authors), and can be used as an indicator of the popularity of the issue

Those are the tickets for the upcoming Trac releases, next-dev-1.3.x, next-major-releases*

Valid tickets for which no release schedule can be set are also listed here (not applicable).

Notes:

• the needinfo tickets have been excluded from this report (see {21}).
• the Chgs_Auths field corresponds to: (number of changes) by (number of different change authors), and can be used as an indicator of the popularity of the issue

Those are the tickets that are scheduled for the 0.12.x and 1.0.x release lines.

Notes:

• the needinfo tickets have been excluded from this report (see also {21}).
• the Chgs_Auths field corresponds to: (number of changes) by (number of different change authors), and can be used as an indicator of the popularity of the issue

This lists tickets that are on the TODO list for a long time.

The criterions for inclusion is that the feature request or bug report is that at least 10 different people participated to the ticket activity.

Tickets are ordered by popularity, defined as the amount of activity on a ticket over time (using a secret formula taking into account the number of participants in the discussion, the number of people on CC:, …)

See also:

• {33} for a similar list but this time with tickets that have been completed (the idea is that eventually all the {32} tickets will move to {33} one day :-) )
• {34} for the list of popular tickets that have received an explicit voted

In order to balance report {32} (tickets that are on the TODO list for a long time), we can also show that we managed to implement popular feature requests over time ;-)

The criterions for inclusion for the feature request or bug report is that at least 10 different people participated to the ticket activity.

Tickets are ordered by popularity, defined as the amount of activity on a ticket over time.

Tickets ordered by number of votes (> 1)

You must be registered to vote.

Those are the tickets closed with a status different than fixed but which have nevertheless a milestone set.

According to TracTicketTriage, those tickets should not be assigned to a milestone.

Those tickets were closed with a resolution of fixed, so provided this is the correct resolution for them, they should also be assigned to a milestone, according to the TracTicketTriage rules.

Show count of opened tickets by type for the next Milestones.

Based on up/down votes

Tickets of interest as a user. That is, tickets that the current user reported, commented on, or marked for CC.

Those are the tickets for the next Trac release, 1.0, 1.0.1, 1.0.2, etc.

Notes:

• the needinfo tickets have been excluded from this report (see also {21}).
• the Chgs_Auths field corresponds to: (number of changes) by (number of different change authors), and can be used as an indicator of the popularity of the issue

Those are the tickets for the next Trac release, 1.4, 1.4.1, 1.4.2, etc.

Notes:

• the needinfo tickets have been excluded from this report (see {21}).
• the Chgs_Auths field corresponds to: (number of changes) by (number of different change authors), and can be used as an indicator of the popularity of the issue