—————- to be translated

Bug Tracker FAQ

The Qt Bug Tracker is a public forum for creating, discussing and fixing Qt bugs, enabling the Qt user community to collaborate with Nokia Qt developers on ensuring Qt remains a high quality framework. We’ve put together a simple guide below to help you get started using Qt Bug Tracker.

You can also take a look at Jesper’s blog for details on the procedure.

1. Creating a New Account

To create a new account, direct your browser to http://bugreports.qt.nokia.com, click the “Signup” link and follow the instructions. Note that your username and full name will be visible to other users, but your email address will not. You can later change the full name and email address registered to your account.

If you want to contribute bug fixes to Qt using Gitorious, it is a good idea to choose the same username and full name as for your gitorious account at http://qt.gitorious.org (see Section 5 – Contributing a Bug Fix).

2. Finding Existing Issues

To find an existing issue, click the “Find Issues” link at the top of the page. This will display the filter pane on the left hand side, which you can use to create a filtered view of the existing issues.

You can for example search for issues based on project, issue type, component, version or text in the issue’s summary or description. Once you are happy with your filter, click the “View >>” button to retrieve the search result.

If you are logged in you can also save your filters by clicking the “Save” link in the filter pane.

3. Creating a New Issue

To create a new issue, please check if the issue has not already been reported by searching in The Qt Bug Tracker. If the issue does not seem to exist already, click the “Create New Issue” link at the top of the page and follow the instructions.

Please provide sufficient details, including auto-tests or example code, for others to reproduce the issue if you are reporting a bug. This will increase the chance that the bug is prioritized higher.

Incomplete bug reports that cannot be reproduced may simply have their status set to “Need more info”, and the bug may not be looked into further until more information has been added.

4. Voting on Issues

To indicate that you want an issue fixed, you can vote for it. You can do this by opening the issue and clicking on the “Vote for it” link in the “Operations” pane on the left hand side. The number of votes an issue has may be taken into account for the scheduling of the issue.

You can also retract your vote later.

5. Contributing a Bug Fix

The Qt Bug Tracker is not the place for contributing code to Qt. Instead, we invite contributions to address issues using the contribution guidelines at http://qt.gitorious.org/qt/pages/QtContributionGuidelines so as to speed up the ongoing improvement in Qt for all.

6. Monitoring an Issue for Changes

When a Qt Bug Tracker account is created a valid email address needs to be supplied. This email address will be used when notifying you of changes to

  • Tasks that you created
  • Tasks that you are monitoring

To monitor an issue click the “Watch it” link on the left side of the form for a given issue.

Note that optionally your Qt Bug Tracker account setting can enable notifying you of changes that were made by you. To change this setting for your account:

  • Click on the link at the top right of the page that indicates your Qt Bug Tracker user name
  • Click the “Edit Preferences” link on left hand side of page
  • Check/uncheck as required the check box named “Email me when I make changes”.

7. Finding an Issue Via Task Tracker ID

To find an issue based on the Task Tracker ID:

  • Click the “Find Issues” button at the top of any Qt Bug Tracker page
  • At the bottom left of the form enter the Task Tracker ID in the field “t4id”
  • Click the “View >>” button to display the Qt Bug Tracker issue that matches the provided Task Tracker ID.

8. How we prioritize bugs

  • P0 – Blocker: MUST be fixed ASAP
    • Issues that prevent further development
    • legal issues
    • serious data loss issues
    • Tier 1 build issues
  • P1 – Critical: Urgent and Important, will STOP the release
    • Regressions from the last version that are not edge cases
    • Data loss
    • Tier 2 build issues
    • All but the most unlikely crashes/lockups/hanging
    • Serious usability issues and embarrassing bugs
    • Bugs critical to a deliverable
  • P2 – Important: Not Urgent, should be fixed, but will not stop the release.
  • P3 – Somewhat important: can be fixed, but doesn’t affect the release in any way.
  • P4 – Low priority: Would be nice to fix, but it’s not very important.
  • P5 – Not important, not relevant and not urgent.