1. eMB Bug-Workflow Bugzilla – User overview
Alexander J. Ludwig, BC / MW
18.Oct.2012
Presentation title in CorpoS Regular 9 pt | Department | Date

2. Use of this document
Bugzilla is the bug reporting tool of our choice. It’s very handy and easy to use.
This document will give you a brief but detailed introduction into the use of Bugzilla.
You can also find information about bug workflow and you may consult this document if you need any information regarding a field in the bug submission form (see page 14).
This document contains:
Test concept/Bug Workflow………………………………………………………….3
Login…………………………………………………………………………………………….4
Entering a bug…………………………………………………………………………..….7
Adding an attachment………………………………………………………..……….14
Appendix …………………………………………………………………………………….17
Search Function – Browse……………………………………………………………20
Searching/Finding an existing bug……….……………………………………..21 Bugzilla – bug status……….……………………………………………………
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

3. 1. Test concept / Bug Workflow
Identify a bug (deviance to the specification) and check if it has not already been reported in Bugzilla (see page 17: “5. Searching / Finding an existing bug”).
2. Submit the bug to Bugzilla. (Screenshot should be attached – see page 9: “3. Entering a bug” )
3./4. The test responsible (Bugzilla-Master) for you Bugzilla product evaluates the bug report.
5. The test responsible forwards the bug to the supplier.
IT Supplier of ITM/FM checks the bug and gives feedback to the Test-Team. Feedback can contain: Bug accepted / Bug not understood (tester will be asked) / Bug not accepted / Reconcilement with the product management (PM) or project leader (PL) necessary.
7. If the bug has not been accepted or needs clarification, the Bugzilla Master arranges reconcilement with the PL or PM.
8. IT Supplier of ITM/FM reports the solution of the bug to the Test-Team.
The tester is being informed about necessary retest. He checks and approves the solution of the bug.
Bugzilla Master closes the bug.
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

4. 2. Login You can get a login and password from the DSCneu test-team.
Please contact Manuela Kröber
Bugzilla URL: 1
On the Bugzilla main page you can choose to login by clicking on the
“Log In” button or you may click the link “Log in” at the top or bottom navigation.
Quick Login
Standard Login 2 1 2 1
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

5. 2. Standard Login 1 2 3 1 4 2 3 4 Enter your login
(usually your address)
Enter your password
Set the IP-restriction option
Click Login 1 4 2 3 4
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

6. 2. Quick Login 1 2 3 1 2 3 Enter your login
(usually your address)
Enter your password
Click Login 1 2 3
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

7. 3. Entering a bug . 2
There are two ways to get to the bug submission form.
Click on File a Bug
Click the “New” link
If you are not on the home of Bugzilla, you can always submit a bug by using.
Note: Before you got to submit the bug, you should look if the bug you are going to submit has not been submitted already. Details on how to search for a bug can be found in chapter “5. Searching” on page 20. 1 1 2 2 2
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

8. 3. Entering a bug Choose the product, where the bug occurs.
Please note: This is a example about the eMB Bugzilla product, your product access can be differnent.
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

9. Click to show all fields !
3. Entering a bug
Click to show all fields !
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

10. 3. Entering a bug continued on next page 1 2 1 2 4 2 3 3 4
Make sure you activated the „Show Advanced Fields“ switch !!!
The component which the bug was found in
 see Description Box
Description of the selected Component
Test environment on which the bug was found.
Severity (leave severity as is). 1 2 1 2 4 2 3 3 4
continued on next page
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

11. 3. Entering a bug continued on next page 5 6 7 5 6 8 7 8
Your platform and your operating system. Check if the system choose it right. If not change it.
The priority of the bug  see appendix. page 17
Don’t change, this is automatically entered and depends on the component which was chosen
CC, possibility to add someone to the CC-list. 5 6 7 5 6 8 7
continued on next page 8
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

12. 3. Entering a bug 9 10
The URL of the page the bug occurred.
A short summary of the bug, this is important to quickly identify the bug. Will automatically search for possible duplicates.
The bug description. Please describe the problem as detailed as possible. Please include the current state and also a desired state (how it should be). 9 10 11 11
continued on next page
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

13. 3. Entering a bug
“Add an attachment”: Here you can add a screenshot that describes a bug. This is helpful to understand the bug. (see chapter 4)
Enter a business case, countries and keywords here. Keywords need to be separated by a blank (e.g. “CCc” or a country). Valid keywords can be found by clicking the link “Keywords” or see appendix page 17.
Click the Submit Bug button to submit your bug and save it in Bugzilla. 12 13 12 14 13
continued on next page 14
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

14. 4.Adding an attachment while entering a bug1
Click “Durchsuchen…” to add a file*. E.g. screenshot to describe the bug.
Add a short description of the attachment e.g. “Screenshot”.
Use “auto-detect” as content type determination for the attachment.
Note: If you want to write an comment for the attachment create the attachment after entering a bug.
*For the attachment you may want to use PowerPoint files. It’s handy if you want to describe steps to the bug with more than one screenshot and text in them. 1 2 2 3 3
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

15. 4.Adding an attachment after entering a bug
Go to your bug or a bug you want to add an attachment. You can get there by searching for a bug or after you submitted a bug you can click the linked bug number. (In this example the link to bug #2430 has been clicked.)
On the bug page there is a table for the attachments. Click the “Add an attachment” link to go to the attachment submission page. 1 1 2 2
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

16. 4.Adding an attachment after entering a bug1
Click “Durchsuchen…” to add a file*. E.g. screenshot to describe the bug.
Add a short description of the attachment e.g. “Screenshot”.
Use “auto-detect” as content type determination for the attachment.
If you need to comment the file you want to add, enter some text.
Click Submit to add the attachment to the bug.
*For the attachment you may want to use PowerPoint files. It’s handy if you want to describe steps to the bug with more than one screenshot and text in them 1 2 2 3 3 4 5 4 5
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

17. 3. Appendix - Entering a bug
Field Name
Contains
Possible selections
Note
Product
DSCneu
Version
Please specify the test
Component
Specify where (in which part of the application) the error / bug occured
Take a look at the description next to the Component selection.
Platform
Computer of the tester
Check if the system chosen correct. OS
Operating system of the tester
Windows, Mac, etc.
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

18. 3. Appendix - Entering a bug
Field Name
Contains
Possible selections
Note
Priority
Rating of the bug relevance P1
Serious deficiency. Excludes a going live and prevents an acceptance. Examples:
There is no pass trough the main process (incl. Pint function). (A workaround to get to the target is not permitted).Responsetime Server/Server >5 sec. P3
Light deficiency. Examples: Light deficiencies in the Layout or the wording, form or layout errors without influence on the functionality.
Severity
Field is not being used.
Assign to
Addressee of the bug
Please leave this field blank (will be autofilled). There are no directly assigned bugs.
URL
URL of the faulty page
Current URL
Please insert the URL of the faulty page. Rightclick  Properties  Copy & Paste
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

19. 3. Appendix - Entering a bug
Field Name
Contains
Possible selections
Note
Summary
Future heading and name of the bug
Summary has to be self explaning and has to include the most important keywords (e.g. error in pdf creation).
Description
This field serves the description of the bug
Best practise is to describe the click path to the bug and afterwards the bug itself. If the path prerequires certain actions of the user please don‘t forget to describe them.
Also don‘t forget to mention the browsers in that you had this bug.
Everything needs to be described and in English.
Keywords
Keywords describe the sub process and the country
Please specify the Keyword (e.g. CCp) and the country (e.g. Österreich (Austria)).
Depends on
Field is not being used.
Blocks
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

20. Search Function - Browse1
Browse function has been added.
First select a product then a component.
The function shows all open bugs of the selected component. 1
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

21. 5. Searching / Finding an existing bug1
Click the “Search” link in the top or bottom bar of the window to go to the search form.
Click the „Search“ button on the Bugzilla home.
Enter your search into the „Quick Search“ input field and press the Quick Search button. 1 2 2 3 3 1
continued on next page
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

22. 5. Searching / Finding an existing bug1 2 3 4 5
Search for a string in the summary of the bugs, use the dropdown to change the search options for the string.
Select the Product.*
Select the components.*
Search for a status* (e.g. new bugs only).
Search for a resolution* (e.g. without resolution “-”). 1 2 3 4 5
continued on next page
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

23. 5. Searching / Finding an existing bug
More detailed searches can be made by opening the different search categories:
Detailed Bug Information
Search by People
Search by Change History
Custom Search
Detailed Bug Information:
Additional possibilities to search for: Comments, URL and Keywords.
Search for a bug number.
Select the test environments.*
Search for a priority* (only P1 to P3 are used.) 6 7 8 9 6 7 8
continued on next page 9
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

24. 5. Searching / Finding an existing bug
Search by People:
Search for a “person” (e.g. bug owner + contains + “Daimler”).
Search by Change History:
Search for changes* in a certain time period (e.g. Assignee changed during the last week)
Click on Search to start your search.
*(CRTL+Click to make multiple selections.) 10 10 11 11 12 12
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

25. 5. Searching / Finding an existing bug
Sort columns by clicking on the suitable header (e.g. sort by “Status”).
Click any bug ID to get a detailed view of that bug. (You can edit the bug or add comments there).
• CSV will give you the current result list as .csv-file download.
• Change Columns will let you change the columns of the result list (e.g. show the reporters mail address or don’t show the resolution).
• Edit Search will let you edit the search parameters you specified before (click here instead of your browsers back button).
You can save the search by entering a name and clicking “Remember search” it will be shown as link in the bottom bar at “Saved Searches:” (e.g. My Bugs). 1 1 2 2 4 3 3 4
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

26. 5. Searching / Finding existing bug
Examples of useful search queries:
Any bug which has no resolution (is not solved)  Go to the search form, select “—” in the resolution box and click on “Search”
Any “Open” bug which is currently assigned to the IT Supplier  Select the components (e.g. if you want all, you don’t need to select anything in the component box). In the “ Addresses and Bug Numbers” box you need to set a check mark at “The bug assignee” and select “contains” in the dropdown menu. Now enter the supplier’s name or address in the text field below and click on “Search”.
Any bug which you have submitted or currently belongs (assigned) to you.  Just scroll down and click on “My Bugs” in the bottom bar at “Saved Searches” Manually searched for this you would need to set a check mark at “the bug assignee” and at “the reporter” in the “ Addresses and Bug Numbers” box. Then you would need to select “is” in the dropdown menu and enter your login name below (your address).
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

27. 6. Bugzilla– bug status
A bug can have different status and resolutions during its lifetime.
Here is an example:
The bug is being submitted by the tester and automatically “assigned” (and forwarded) to the test coordinator. A newly submitted bug will have the status “NEW”.
The test coordinator checks the bug and assigns (“assigned”) it (if necessary) to a service provider. The status will stay “NEW”.
The respective service provider checks if he can fix the bug. If this is the case, it is necessary that the bug is set to “ASSIGNED” by the service provider, so it is obvious for all involved parties that the bug can be solved and who the responsible person is. Afterwards the bug is beeing fixed by the supplier.
If the service provider does not feel responsible, , he set the Bug to Status “RESOLVED” resolution “invalid” with a comment. This is also need when the service provider need more information from the bug reporter for the bug.
If the bug was fixed, its resolution will be set to “fixed” and the status will be “RESOLVED”.
If the bug was not fixed because its not a bug (referring to the specification) the resolution will be set to “invalid” and the status will also be changed to “RESOLVED”.
Now the bug reporter has to retest his bug. If he accepts the bug as “RESOLVED”, he has to mark it as “VERIFIED” and later the test coordinator will set the status to CLOSED.
If the bug is not fixed, it has to be “REOPENED”.
Note: You can only change the status if you leave a comment at the same time (e.g. after retesting a fixed bug and marking it as “VERIFIED”, it‘s enough to leave a comment like „checked…“ or „OK…“ and adding the according environment).
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date

28. 6. Bugzilla – bug status Bugzilla Status Bugzilla Resolution Meaning
Responsibility
NEW -
The bug has newly been entered or has been reassigned. At first, it is addressed per default to the QA-contact and will be addressed to the correct responsible (during a release test period via a so-called Bug Review Meeting (BRM), otherwise by the QA-contact).
Bug Reporter
ASSIGNED
The bug has been accepted by the assignee that he will take care about (and later fix) the bug. Primarily, this status explicitly indicates that the bug will be finally handled by the assignee. (The actual bug fixing can take place later.)
Assignee
RESOLVED
FIXED
The bug has been fixed and successfully retested on an official test environment by the bug fixer. I.e. now the bug can be retested by the bug reporter on the test environment mentioned by the bug fixer.
Bug fixer
INVALID
Either the bug is no bug („Works as specified“) or it could not be reproduced or there are insufficient information about the bug (e.g. no Screenshot added).
DUPLICATE
The bug already exists (with another number).
REOPENED
If the status „FIXED“/“INVALID“/“DUPLICATE“ does not match with the underlying specification or the bug is not properly fixed / still exists, the bug reporter reopens the bug.
VERIFIED
FIXED / INVALID / DUPLICATE
Either the bug reporter has successfully retested the bug or he accepts the bug as being invalid / a duplicate of another bug.
CLOSED
The Administrator closes the bug.
Bugzilla Administrator
Bugzilla Intro | BC / MW |
Presentation title in CorpoS Regular 9 pt | Department | Date