This page allows user to enter report details about his CGM bug.
There is a “[?]” for complex rubrics. It enables user to have a description about the rubric meaning.
When you have a “*” near the rubric name, it seams that you absolutely have to complete it.
Rubrics:
Summary (required + documentation): “A brief one line description of the problem. Help out the developer by actually making it descriptive and meaningful.”
Keywords (documentation): It will be used for bugs search and management.
Involved tool: Enable to specify which tool is involved with the reported bug.
Version: Involved tool version (1.0, …).
Platform: Choice between PC, Mac and Unix.
OS: Choice between WinNT, Win2000, OS X.
Description
(required + documentation): “A detailed description of the
problem.
(As a rule of thumb you should always enter enough
information for the developer to feel like he is in your shoes.
Describe what you were doing, what you expected to happen, what
should have happened, the error, setup and system settings, software
version(s), and possible ideas and suspicions.)”
Workaround (documentation): The user can propose a workaround to the bug to achieve the task without triggering the bug.
Expected date for a correction.
Additional information.
Upload file: CGM, …
Your e-mail (required): this address will be the user login.
In order to save the report the user has to click on “Submit Report”.
Example: