Bugzilla offers several ways to search for bugs, catering to different levels of information you have about the bug:
1. Quick Search:
- This is the simplest way to search. Just type a word or series of words in the search box. Bugzilla will search the Product, Component, Keywords, Alias, Summary, Whiteboard, and Comment fields for your word(s).
Typing a number will take you directly to the bug with that ID.
- Adding more terms narrows down the search (AND search).
- Searching is case-insensitive.
2. Simple Search:
- Similar to Quick Search, but with a dedicated page.
- Good for finding a particular bug when you have some keywords.
3. Advanced Search:
- This is the most powerful search method.
- You can specify criteria for various fields like Product, Component, Status, Resolution, Summary, Comments, URL, Whiteboard, Deadline, Bug Numbers, Version, Severity, Priority, Hardware, OS, and even custom fields.
- You can combine multiple criteria to narrow down your search.
- Allows searching by people (assignee, reporter, cc member, commenter) and change history.
4. Custom Search:
- Lets you create complex queries with specific fields, operators, and values.
- You can combine terms using "Match ANY" or "Match ALL" and use parentheses for grouping.
Tips for Effective Searching :
- Be specific: The more specific your search criteria, the more accurate your results will be.
- Use keywords: Think about the words that might be used to describe the bug.
- Use wildcards: You can use the asterisk (*) as a wildcard to match any string of characters.
- Search in specific fields: If you know which field the information you're looking for is likely to be in, you can specify that field in your search.
- Combine search methods: You can use a combination of Quick Search, Simple Search, and Advanced Search to find the bug you're looking for.
Remember that Bugzilla's search functionality might have some specific syntax or features depending on the version and configuration. You can usually find more detailed information about searching in the Bugzilla documentation or help resources.
