Excellent stuff, my thanks to all involved :)

good.. but we can change it anytime if another system can be suggested...

Excellent, works very well.

I shall ask next time if they have any preferences.

ok ;)

IMHO we need a "guideline" for bug reports, e.g. https://developer.mozilla.org/en/Bug_writing_guidelines

We really need quality bug reports, especially as the developers are not part of the system, i.e. they do not interact with the reporter, they only read the report.
A low quality report might be written in 1-2 minutes, but the workload for the admins or developers are increased considerably. If one wants to report a bug that he things is important he should take the time to write a high quality report.

For aircraft system this includes researching the subject and providing evidence. There are so many bug reports on aircraft systems in this forum that a simply wrong and not or bad researched.
For game bugs this requires a step by step instruction to reproduce the bug.
The reporter has to provide (depending on type of issue)
- step by step instruction to reproduce the issue
- screenshots to display the issue
- mission files/tracks to allow easier reproduction of the issue
- documents/sources to proof the issue

It looks like at dev-heaven they have votes showing in issues list on the right-hand side https://dev-heaven.net/issues

hhmmm... is this a free plugin or they made it for them? need to discovery...

S! Added to the 1st post of the thread.

Thankyou Ataros, I hope the dev's will use the bugtracker. I've posted one issue but first time I entered info the new issue form screen refreshed & info disappeared. The second time I entered info the form completed correctly, however, there are now 2 versions of the issue on the DB. Could you look at the setup with a view to correcting this problem. :)