Bugzilla on Debian 12 (x86) with support by Fleximg

AWS-Marketplace

https://aws.amazon.com/marketplace/pp/prodview-4ortdghhfoyz6

Usage Instructions

*Note
Before you start to access the system, please ensure the Status Checks of the instance in the AWS Console turns to 2/2 checks passed, or the initialization process might be interrupted and the software configuration fails. It takes about 3-5 mins.

1. Login user or create user

Open the Bugzilla home-page and enter the login details

http://{your-host-ip}/bugzilla

Enter your email and password in the Enter Email and Password field to log in

User: Fleximg@gmail.com

Password: Fleximg!123

Image_1

You can also create a New Account by clicking Open a New Account. After entering
the email address, you will receive an email for creating a new account.
Clicking the address will enter bugzilla to edit the password and account information

Image_2

2. Edit bug

Image_3

Image_4

Image_5

*Note

  1. The initial status is generally uncomfirm without confirmation by Assignee

  2. By default, assingee is the person in charge of the product's component

  3. The CC object is the copyist. This role does not change the bug,
    but he will be notified by email each time the bug status changes.
    Usually the leader or the person in charge of the entire project,
    but not responsible for fixing bugs.

  4. The difference between Severity and Priority:

Severity: The severity of a bug to the function

Priority: How much a bug affects the business

3. Test flow example

Finished bug writing interface

Image_7

After the bug is edited, Assginee, the cc object, receives an email.

After modifying the bug, edit the description, status and handling suggestions after the bug is solved.

Image_8

After Assignee fixes a bug, reported will receive an email notification,
search for a corresponding bug in the search, and test the bug again.
If the test finds that the bug is solved, the status is changed to verified,
and the processing comment is closed.

Image_9

Image_10

4. Permission setting of a role

After Assignee fixes a bug, reported will receive an email notification,
search for a corresponding bug in the search, and test the bug again.
If the test finds that the bug is solved, the status is changed to verified,
and the processing comment is closed.

Image_11

The above tutorial describes the use of the process, more detailed tutorials refer to the official tutorial https://bugzilla.readthedocs.io/en/5.0.4/using/index.html

- Start apache2 service: `sudo service apache2 start`
- Restart apache2 service: `sudo service apache2 restart`
- Stop apache2 service: `sudo service apache2 stop`
- Check apache2 service status: `sudo service apache2 status`

- Start mysql service: `sudo service mysql start`
- Restart mysql service: `sudo service mysql restart`
- Stop mysql service: `sudo service mysql stop`
- Check mysql service status: `sudo service mysql status`