A Software Performance Report (shortcut SPR), is the uniform method by which defects (Bugs) in DraftSight are reported. Meaning if you report a DraftSight issue to us, trough the Report a Problem button (Getting Started) we write an SPR to forward the issue to the Development Team, after it has been verified by our Technical Support Team. Each time a user lets the Support Team know about a specific issue the Technical Support Engineer writes a SPR with the steps to reproduce the issue or attaches a customer hit to an existing SPR. So if e.g. John Doe reports an issue, and this issue has not been reported before, we write an SPR to let development know about this kind of problem. If another person reports the same issue again, we attach another customer hit to this existing SPR. The number of hits will increase the chances that this issue will get fixed soon. Please note that each issue can just be reported once by a person.

Naturally, a bug being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources. So when reporting issue to us please bear in mind that we need the following information in order to reproduce the problem:

In problem reports, try to distinguish between facts ("I was at the computer and this happened") and speculation ("I think the problem might be this"). Leave out speculation if you want to, but don't leave out facts! When you report a bug, you are doing so because you want the bug fixed, and the bug may get fixed more quickly if you help by supplying all the information you can. “It’s not working” does not help us to troubleshoot the problem; we need facts in order to help you.

The basics: what you did, what you expected to happen, and what actually happened.

Those are the three basic elements of a bug report. You need to tell us exactly what you did (for example, "Print the attached file with PDF printer"), what you expected to have happen (“PDF file with all the information from the original file”), and what actually happened ("Missing geometry in the resulting PDF file"). Also please don’t forget to let us know which version and OS you are using. E.g. Winx64 V1R3.2.

By telling us which version you are using, what you tried to do, what you expected to get, and what you actually got, we don't have to guess.                                

 Thank you for helping us to improve the DraftSight experience!

A list of closed and verifed fixed bugs can be found in the Release Notes. The newest available Release Notes as of today can be found here: Release Notes V1R3.2.

SPR Status Key