Bug Reporting Guidelines

[WHMCS Chris]

In order to assist the WHMCS Development team, we've generated a list of guidelines to allow us to better isolate the issue, replicate, and address. We respectfully request appropriate following of these guidelines.

Bug submission titles should include a brief, but detailed statement of the issue. Bug submission titles should also be prefixed with [uNCONFIRMED]. This allows the development team to review the threads in this community section and isolate potential issues that have not been reviewed.

Ex: [UNCONFIRMED] Tax rules not being applied to hidden products when manually added

Submissions subjects should include a separated description of the issue and how it's affecting the current BETA version.

Ex: Tax rules applied to a hidden product are not being automatically added when adding orders via the admin area. While manually ticketing to apply tax provides a usable work around, this box should be ticked by default as it was in previous versions.

Submissions should also include detailed steps to replicate the issue.

Ex:

[1] Assign tax rules to a product

[2] Make the product hidden from the order form

[3] Add the hidden product to a client from the admin area.

[4] Observe that tax rules are not applied during invoice generation

Note: Applicable screen shots or videos are also welcomed.

In order to further assist, below is a template that can be used during the submission process:

 

===========DESCRIPTION=========== 

 

=========STEPS TO REPLICATE=========

  

=======ADDITIONAL INFORMATION======

 

Once a bug submission has been reviewed by the development team, if found to be a valid bug, a case will be logged internally and the community topic changed from [UNCONFIRMED] to [CONFIRMED], and the case number provided. While a patch may be supplied, WHMCS reserves the right to provide fixes to cases within the following releases for that branch.