
So, according to these statistics, Clonk-Karl is by far the most busy bug-eater :-). And who reports the most bugs? That will be me, of course. Dunno if that is such a good thing though ;-) - I'm just using it to keep track of the work we still got to do.
> Access Denied.
:(

Edit: Fixed. Developers can look at the graphs now.

> Access Denied
It is still the issue
It works for me FWIW

Me not. :-(

P.S. Which leads to the thought: Why is this so important?
Uhm, why is not everybody allowed to see the statistics?



> because the graphs [...] are only valuable for the devs to evaluate their work(flow)
It also shows reporter statistics. And the developer statistics might also be interesting to any user, even if it's just informative.
> I'm not sure if the devs are OK with them being "evaluated" like this in statistics for everyone to see.
This is bullshit. The information is public anyway, it's just "harder" to aggregate them. At least to me this is not about "evaluating" something. As I said: If someone wanted to do this then they could do so anyway. Please. This is OpenClonk. Development is public, so we should not try to hide certain things.
I didn't want to have a private board. But if you announce something that nobody but the developers cannot access anyway then this is one of the few things that would actually would belong there instead of the public announcement board.

FYI: When posting this, I didn't even realize that it is intended only for admins. The option to change the permission to access the statistics does not even exist, I had to change it directly in the database.

>because the graphs seem to take quite some time to generate
So there should be some cached version for non-developers, which is updated daily?

> Dunno if that is such a good thing
Well, it is not a very good thing if anyone is willing to hold competitions :-) but it is surely a very effective way of monitoring the ammount of work which is still to be done.
Personally, I liked the "Most Active" and "Most Open" parts which helps to determine the bugs which are going to be resolved in the first place and also helps to see bugs so ancient that everyone has already forgot about them.
Have some misunderstanding about why are "closed" and "resolved" statuses doubled in "Summary" section (which does not make a very big sense) but the new line helps a lot to see how many issues are still to take care of...
In short, a helpfull improvement for the bugtracker which (as stated below) probably needs to be seen by anyone
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill