Edgewall Software

Milestone not applicable

admin/console

2 / 2

admin/web

2 / 5

attachment

1 / 1

general

17 / 30

plugin/mercurial

7 / 9

plugin/spamfilter

8 / 21

project

4 / 6

report system

0 / 2

ticket system

4 / 7

timeline

1 / 1

version control

3 / 6

version control/browser

0 / 1

version control/changeset view

1 / 1

web frontend

2 / 2

web frontend/mod_python

2 / 4

wiki system

1 / 7

The not applicable milestone is a special milestone which is currently used to distinguish between tickets that have not yet been triaged (see TracTicketTriage) and those who have, but for which there's no "real" milestone deemed to be adequate.

This can happen in the following situations:

  • for SpamFilter and TracMercurial plugins, which are not formally associated to a Trac release (WebAdmin plugin related issues are associated to 0.10.x milestones, as for 0.11, it's not a plugin anymore but a component of Trac core)
  • for bugs concerning a 3rd party software (like Subversion), which are occurring frequently enough to be kept opened and documented here, until an external resolution is found (when closing such tickets as wontfix is not really an option, as this would discourage people for following the progress, reporting the workarounds, etc.)
  • for tasks to be done on t.e.o (usually in association with the project component)

OTOH, blue sky ideas are still to be targeted for 2.0.

Note: See TracRoadmap for help on using the roadmap.