Web Development - UD Application Help Pages

Bugzilla: Search for bugs / Create a query

Questions should be directed to Web Development, it-webdev@udel.edu


  1. From the Welcome to Bugzilla page, click on the first link for Query existing bug reports. View Welcome to Bugzilla image

    -- OR --

    From any of the Bugzilla pages, click on the link for Actions: Query in the yellow box at the bottom of the screen.


  2. Enter your query specifications on the Search for Bugs form. View Search for Bugs image

    You don't have to complete any field on this page that you don't need. Completing fields will limit your search, so the less fields you complete, the more bug reports you will need to scan through in the search results.

    Here are some of the fields that you may find helpful:

    • Summary: search for text in the bug summary field.
      The summary is a brief descriptive title for the bug report.

    • Product: Search only bugs within a specific product category.
      The most common IT-WD projects are included in the following products:

      • Form Data Processor: UD Form Data Processor.

      • JSP Forms: UD JSP Forms.

      • Servlets: University of Delaware java servlets.

      • WebForms: University of Delaware's java based web forms.

      Tip: Use CTRL-click to select multiple options.

    • Component: Search only bugs associated with a specific project.

    • A Comment: Search for text in the additional comments field.
      Tip: Additional comments can get quite extensive in bugs, so this type of search can take a long time.

    • The URL: Search for a specific web page entered in the bug's URL field.

    • Status: Search only for bugs with the specified status.

      • Unconfirmed: IT-WD has not validated that this bug needs to be fixed.

      • New: No one has acted on the bug since it was submitted or changed.

      • Assigned: The bug is being worked on.

      • Reopened: The bug was once resolved, but the resolution was deemed incorrect.

      • Resolved: A resolution has been made, and it is ready for testing.

      • Verified: The resolution has been tested and approved.

      • Closed: The bug has been resolved.

    • Resolution: Search only for bugs with the specified Resolution.

      • Fixed: The bug is fixed, and it is ready for testing.

      • Invalid: The problem described was determined not to be a bug.

      • WontFix: The problem described is a bug which will not be fixed.

      • Later: The problem described is a bug which will not be fixed until later.

      • Remind: The problem described is not currently being worked on.

      • Duplicate: The problem is a duplicate of an existing bug.

      • WorksForMe: The problem described in the bug was not able to be duplicated.

    • Email and Numbering: Search for bugs associated with an email address.

      Select the checkboxes for the roles that you want to search, and enter the email address in the open field. You can search for up to two different email addresses. If you specify both, then only bugs which match both emails will be presented in the search results.

      • Bug owner: The person currently assigned to the bug.

      • Reporter: The person who created the bug report.

      • CC list member: A person copied on the bug report.

      • Commenter: A person who entered Additional Comments on the bug report.

    • Bug Changes: Limit the search to bugs changed within a specific number of days, or to bugs where a specific field was changed during a specified time period.

  3. When you are ready to submit the query, click the Search button at the bottom of the page.

Next step:

After you click Search, a Bug List page will be presented. View Search results image To view a report, click the bug number.