You would like to report a bug on a KDC product? If you follow those steps it will be easier for me to keep track of what work, what doesn't and what needs to be done.
Once logged in the bug tracker, click <Report Issue> and fill the form as best as you can:
Choose the right project (it is the product name, or a product family)
Choose the right category if more than one is available, in the case of a large product, you may choose here a specific item.
Be honest with the severity/priority of the problem, some problems ARE more important than others.
Fill out the Description of the problem as precisely as possible, include a chatlog if the script is saying something wrong.
The first aim of a bug report is to let the programmer see the failure with their own eyes. If you can't be with them to make it fail in front of them, give them detailed instructions so that they can make it fail for themselves.
In case the first aim doesn't succeed, and the programmer can't see it failing themselves, the second aim of a bug report is to describe what went wrong. Describe everything in detail. State what you saw, and also state what you expected to see. Write down the error messages, especially if they have numbers in.
By all means try to diagnose the fault yourself if you think you can, but if you do, you should still report the symptoms as well.
Be ready to provide extra information if the programmer needs it. If they didn't need it, they wouldn't be asking for it. They aren't being deliberately awkward. Have version numbers at your fingertips, because they will probably be needed.
Write clearly. Say what you mean, and make sure it can't be misinterpreted.
Above all, be precise. Programmers like precision.
The process is pretty much the same as posting a bug report, but with a different severity (feature).
