Aabel™ NG Support Information

Bug Report Submission

Aabel NG Logo

Describing How to Reproduce a Bug
  • Taking the time to create a detailed bug report ensures that your report will get prompt and efficient attention.
  • Some bugs may be triggered under very specific circumstances associated with one's settings, one's data, or interference from non-Gigawiz background services one is using.
  • Please see the bug report submission guide below.
Bug Report Submission Guide

Please be as detailed as you can when describing how you found the bug and make the bug report easy to understand:

  • Avoid using jargon or abbreviations.
  • Try to remember what you were doing when the problem happened and the order in which things occurred.
  • Provide step-by-step instructions for reproducing the problem (if you have difficulty following your own steps for reproducing a bug, chances are we will find it difficult too).
  • Adding the following items to a bug report can provide useful information and help diagnosing the problem:
    • The document in which you have encountered the bug (e.g., viewer, worksheet)
    • Screenshots of the problem (if applicable, e.g., displaying a drawing glitch)
    • Crash log (if you have encountered a crash bug)
  • To report suspected bugs, copy the form below and paste it into e-mail, provide the required information, specify "Bug Report" in the subject line, and attach any document or screenshot that can help reproducing the bug.


==============================================
End-User Information:
==============================================
Your name:

Product name and product version:

==============================================
Hardware platform and OS version:
==============================================
Operating system version:

==============================================
Bug Type:
==============================================
Crash_____________
Functional problem_____________
Cosmetic_____________

==============================================
Description/Steps to Reproduce the Bug:
==============================================
1.
2.
3.
Etc.

==============================================
Results:
==============================================
Expected Results:

Actual Results:

==============================================