Hi everyone:

after all these years working with TestLink, I've seen tons of issues reports, and unfortunatelly there is still people that do this reports in a way that makes our work extremelly difficult.

I think is important to undertand that issue reporting is not an easy task.

Providing good information in order to allow development team do work in effective way is crucial.

IMHO  info presented in this link can help you (users) and us (dev team) a lot.

(taken from http://www.wolfcms.org/discover/how-to-report-issues.html)

Reporting an issue is fairly simple.

However, the more information you give us, the better we’ll be able to reproduce and fix the problem. When the issue report is unclear, we’ll ask for more information.

In the event that you are unable or unwilling to help clarify the original report, we may be forced to close the issue without being able to properly solve it.

So, when you describe the issue, please focus on answering the following questions:

• What steps will reproduce the problem?
• What is the expected output? What do you see instead?
• What version of TestLink are you using?
• What PHP version are you using?
• On what operating system are you using TestLink ?
• What database are you using? (please include the version number as well)

You may include screenshots if you deem this to be necessary for a complete report.

Remember that less effort/details you put on your issue description =>  higher probability we will choose to assign a low priority.