Description of use of the defect tracking system bugtracker. Net (Extended metaweblog API)

During the development of a calendar project, there will be modification and maintenance requirements from Different developers and testers. When there are few project members, the defect management is usually handled by email and excel, however, if there are more than one person, it will appear chaotic and have no clue. To this end, we have introduced the defect tracking system bugtracker.

The following describes the usage:

The home page is the logon page:

Enter the password and account to log on;

The following is the logon interface:

Each submitted defect (Bug) corresponds to an ID number. When there are many records, if you remember the ID, you can directly jump to the ID at the top, enter the ID number and press enter to view it;

Flag: you can add a flag to the front of the defect records that need to be marked with emphasis (click the corresponding record box)

Description: The title of the released defect record (the title and content of the defect record are the same as those in the same email)

When you move the mouse over the description, the body of the defect is displayed in the pop-up box:

Category: Submission records are classified into the following four categories:

• Defect (Bug): This is one of the most commonly used ones; modifications to a problem;
• Enhancement: a function is not a defect, but needs to be improved due to the needs of the project;
• Question (question): consult other developers;
• Task: the assigned project development task;

Submitted by: the person who submits the defect;

Priority: divided into three levels: High, Medium, and low. It depends on the submitted content. If there is no special need, select "low" when submitting a question ";

Handling: Who should handle the submitted defects;

Status: the status of defect handling is classified into 5:

 

• New submission: Defects released by the defect submitter;
• In progress: the processor has seen this record and is modifying it. However, the problem is complicated and takes some time. The handler can change the defect status to "in progress ";
• Modified: After the defect is modified, the handler sets the defect status to "modified". Then, the tester tests the defect;
• Re-opening: The tester tests the modified defect. If any problem persists, the record is set to "re-opening" and the handler continues to modify the record (after the record is completed, still set to "modified ");
• Close: The tester tests the "modified" defect. If no problem exists, set this record to "closed ";

Note: After the defect handler modifies the defect, the record cannot be set to "closed ";

The top left is the defect record filter:

 

• Open bug modification: All records whose defect status is not "closed" are selected;
• Include attachment: The defect record contains the attachment;
• All bugs: All records;
• Submission duration-status: view the time after submission of each record and the status currently processed;
• Need to be processed: select the record whose handler is the login user;
• Modified-to be tested: select the record whose status is "modified;

Print the bug list, and print the bug details to print the current display record into an HTML webpage (this function is quite useful for developers who are slow to access the server network, you can print the records to be processed and submit them on the web after they are processed );

Add defects:

The following is the page for adding defects:

When submitting a defect, you must write a description and body, and select the defect category, priority, processor, and status;

Note: Use/save in the upper-right corner is very useful. When you select a category, priority, processor, and status, you can use save to save the current selection. The next time you need to use the same selection, click User;

For defect addition, if it is just text, it is easy to add it through the Web. If the image is included, this interface is not very suitable. To do this, the following method is provided:

1. Use a third-party plug-in (bugshooting), and then directly send it to the interface to add defects;

2. for ease of use, I developed a metaweblog API interface for this bugtracker. You can use livewriter to submit defects (this method is recommended if the submitted records contain multiple graphs );

3. You will be able to submit defect records by email (not supported currently );

 

For troubleshooting, click the corresponding description Title to go to the defect adding interface, which is convenient.

 

Starting URL: http://blog.donews.com/me1105/archive/2010/12/04/65.aspx

Over