Community bugtracker is up @ il2bugtracker.com

[Artist]

I'm sorry, but probably did something wrong: I registered as "Artist" and then tried to login, but was rejected with "Invalid user or password". If I click on "Lost password" I do get an email (with my username "Artist"), I can change my password, but am still rejected in the login screen.

Tested with firefox and chrome. Cookis are allowed and set. Feel kind of stupid.

Artist

[ZG15_FALKE]

I suggest we have a project for every release.

Within on of those projects the incoming bug reports should be checked for being provided with the necessary information.
Only after being checked and being complete in terms of necessary information provided, a bug report should then be assigned to Luthier for nearer observation and feedback requests or status info concerning this bug report.

Otherwise dev team gets spammed and will soon loose interest.
Providing all necessary information for a bug report should be done by the community to get some workload impact off the devs shoulders.

Maby this is a topic which is to be talked about e.g. via TS / Skype?!

[ZG15_FALKE]

Originally Posted by Artist

I'm sorry, but probably did something wrong: I registered as "Artist" and then tried to login, but was rejected with "Invalid user or password". If I click on "Lost password" I do get an email (with my username "Artist"), I can change my password, but am still rejected in the login screen.

Tested with firefox and chrome. Cookis are allowed and set. Feel kind of stupid.

Artist

check for registration email first, activate and be habby ?

[PE_Tigar]

Excellent idea - I have a bunch of stuff to report.

[41Sqn_Banks]

Suggestions for changes in issue categories:
3D models (cockpits and ext.) --> should include all types of objects and skins, suggestion 3D models and skins
AI and communication --> as is AI and communication
Aircraft performance and FM --> typically goes hand in hand with DM, systems and controls, suggestion Aircraft FM, DM, systems and controls
Aircraft Systems Errors --> duplicate Remove
Damage model --> visual DM is covered by 3d model, negative effects are covered by aircraft FM, duplicate Remove
FMB and scripting --> as is FMB and scripting
Graphics --> Graphics and visual effects
Interface --> User interface and menu
Online multiplayer specific --> Multiplayer specific
Sound --> as is Sounds
System/critical --> we shouldn't use severity as a category, better General
New --> Maps
New --> Singleplayer specific

Maybe we should add a own project for issues with the bugtracker.

[Artist]

Uups... there's something...

Originally Posted by ZG15_FALKE

check for registration email first, activate and be habby ?

...in my spam folder.

Originally Posted by Artist

Feel kind of stupid.

Now I know why.

Artist

[41Sqn_Banks]

Originally Posted by ZG15_FALKE

I suggest we have a project for every release.

You mean one project for every release version? Or one project for CoD and one for sequel (aka BoM)?

Within on of those projects the incoming bug reports should be checked for being provided with the necessary information.
Only after being checked and being complete in terms of necessary information provided, a bug report should then be assigned to Luthier for nearer observation and feedback requests or status info concerning this bug report.

Otherwise dev team gets spammed and will soon loose interest.
Providing all necessary information for a bug report should be done by the community to get some workload impact off the devs shoulders.

Agreed. I don't think we can enforce a high quality standard for incoming reports. Therefore only reviewed bug reports (confirmed, complete, ...) should be assigned to luthier or one of the devs. It is possible to allow only admins/moderators to assign a report to a person?

[ZG15_FALKE]

Originally Posted by 41Sqn_Banks

You mean one project for every release version?

I would suggest one project per released version and correspondingly named. Makes it easier to keep trrack for which version/bugfix the bug or feature was reported/requested.

Originally Posted by 41Sqn_Banks

It is possible to allow only admins/moderators to assign a report to a person?

Yes, sure is!

[41Sqn_Banks]

Originally Posted by ZG15_FALKE

I would suggest one project per released version and correspondingly named. Makes it easier to keep trrack for which version/bugfix the bug or feature was reported/requested.

I've seen that it is possible to add a new versions in the settings. Don't know if this is the feature you are looking for.

Yes, sure is!

This should do it. IMHO reporters don't need to assign a issue. The managers/moderators could manually assign a issue or use the auto assignment by category to assign it to a certain manager/moderator that is responsible for reviewing it. After review it is assigned to luthier.

[Ataros]

Originally Posted by 41Sqn_Banks

Maybe we should add a own project for issues with the bugtracker.

Please feel free to create one if you know how. Maybe we can get luthier's opinion on the categories there.

To me Preformance, FM and DM, systems and and controls are different. The rest I agree with.

is there a forum in the system? If yes, we can ask luthier there what is better for them and easier to use.