Skasi :
quote: I clearly said "forum search" and forum-search using the search bars that only pop up in the forum DOES WORK PERFECT |
However it was not about the 'search bars' (Filter: thingys)
https://github.com/ZeroK-RTS/Zero-K-Infrastructure/issues/871 reads:
this is about the search input field in the top-right of zero-k.info and not about the forum's "Filter" input field.And I also refered to the SEARCH with the looking-glass-icon and not to the two FILTER fields.
quote: I do not think the player-side is going to be done much better than it is now though. The only extra we would get out of players is: Better thread names. Infolog. Maybe a screenshot.
|
That would already be a good step.
Graphical bug = screenshot. Obvious!
If people can post screenshots in "ingame fails" thread they can post it as bugreport, too.
http://zero-k.info/Forum/Thread/1784?postID=150004#150004Other things could be simple tests that most player can do:
-Press F5 to turn UI on/off
-Disable LuaUI / disable LuaRules
-How to cheat units, to reproduce situations (instead of 90min replays)
-widgets on/off etc, trying different settings
-In general signaling to players that bug reports are welcome/needed.
Not all players would do such things, but some would, especially those posting much.
It is not strictly only about bugs, but also noobtraps and such.
quote: Do you actually have a problem with the Zero-K repository bug tracker? |
With the software? No.
With how it is used? Yes.
I had already posted on that during the move from google-code to github. (Maybe that worked a bit, because at least it is not that chaotic anymore)
quote: In past bugtracker we didn't close issues |
Yes, was bad.
quote: The "My music has gone" bug seemed to be handled about as well as could be expected. What would have improved that situation? |
No youtube music links.
Better awareness that if you know of a workaround for something then report it, so workaround will not be nessecary.
More people filtering forum posts to bugtracker.
quote: - If original poster is able to reproduce, closing the ticket gives him known feedback is required. He can respond and ticket can be reopened if he does. ... If however all devs failed to fix it -> close and wait for repro steps seems ok. |
No, in both cases you set it to "Feedback needed."
If there is no feedback for a while AND no new reported cases THEN it can be closed it as "could not reproduce."
Otherwise you have situations as in
https://github.com/ZeroK-RTS/Zero-K/issues/1091 where the ticket is closed, someone posts more details -- And nobody sees it.
(Do not say that it was re-opend. It was re-opend right now because Orfelius mentioned it in this thread. Before that nobody noticed it for 16 days)
quote: - If some other player encounters the bug and he decides to report it, he wont search he will just create new ticket with or without repro steps. |
That is why you tell them to search before posting. (Not such a strange concept anyway) Shows why good titles/text matter: so they are found with search.
Imo it is also bugtracker misuse which leads to very strange assumptions about project status. Like the "release on steam in two weeks" posts. Or last month Licho posted something how the current lobby was good enough for release?! How do those assumptions happen? I can look in bugtracker see 234689 bugs, kinda know that many more probally went unreported. If it is not a bug but 'only' a missing feature then it is not not tracked at all.