Bug Tracker

Using the Mercurial bug tracker.

1. Finding the right bug tracker

Bugs are often caused by a GUI tool or extension. If you believe this to be the case, it's best to report the bug there first.

2. Getting started

Mercurial's bug tracking system is located at http://mercurial.selenic.com/bts. It's used for tracking known bugs, requested features, and wishlist items.

Most bug tracker usage will need you to register an account so that you can get updates on your bug reports.

3. Creating a new issue

<!> Before filing a new bug, please use the search form to try to locate similar bugs.

To create a new issue, click "Create New" under "Issues" in the sidebar. Put a specific summary of your issue in the title.

3.1. Choosing a priority

Please try to select the most appropriate priority:

(A regression is defined as a bug that breaks something that worked in earlier releases.)

3.2. Information it's often helpful to include in your description

4. The life cycle of a bug

As a bug is tracked, it will go through various states, some of which will demand your attention:

Issues in the need-eg and testing states will get marked resolved if there is no further activity.

<!> Don't comment on a resolved bug, it will reset the state to chatting!

5. Etiquette

See ManagingBugs for the developer side of the process.

CategoryBugs CategoryProject