Login | Register
My pages Projects Community openCollabNet

Subclipse Issue Tracker

Issue Tracker Guidelines

Before filing a new issue, please:

  • Re-read the Subclipse on-line help within Eclipse
    (also the FAQ and the online Subversion book).

  • Look through all existing issues, or search their summaries:

    to see if this bug has already been reported.

  • Report your problem to users@subclipse.tigris.org,
    describing the bug or feature request that you were about to file. People there will ask you questions and help get the bug report into a useful form, after verifying that a new issue is appropriate. (See here for how to write a useful bug report.) If you do file an issue, remember to include a link to the relevant mailing list message(s) or thread. That's important context for anyone reading the issue, and its presence also confirms that the issue has already been discussed on the mailing list. Otherwise, the issue may get accidentally closed because no one can tell that it is the product of a list discussion.

We depend on the mailing list as a first level of filtering for our bug tracker. Without it, the tracker would be full of duplicate issues, non-issues, and unreproducible issues. Please help us keep the bug database clean, by always posting to the list first!

When mailing the list with a concern, make sure that your e-mail describes your bug or enhancement fully. Provide details about the versions of the relevant software (Subversion, Subclipse, JavaSVN etc.) that you are using, about your operating system, and about any other thing that might seem pertinent to the issue. If you can provide a script which consistently reproduces a problem, that can be incredibly helpful to those evaluating and/or working on your issue.

Finally, be sure you are subscribed to the mailing list (which is low traffic). If you are not subscribed, your message to the list will not go through until it has been moderated, and the default mailing list configuration only sends replies to the users that are subscribed to the list. Messages are typically answered in less than 24 hours so check the list archive if you have not received a reply.

Filing New Issues, Modifying Existing Issues

You must be logged in to the web site to add a new issue, and you must be logged in with the Observer role in the Subclipse project to modify an existing issue — even one that you created yourself.

Here's how to acquire the Observer role:

  1. Log in on the tigris.org site
  2. Go to the Subclipse project front page
  3. Click on the Request project role link directly below the "Project Home" line
  4. Request the Observer role
  5. Wait for the confirmation e-mail

Enter the Issue Tracker

And so, with further ado, we give you (drumroll…) the Subclipse Issue Tracker.

Again, remember that to add or modify issues, you must be logged into the website.