3288 active members
  208 are online
Year Day Time
14 177 1:59:22
Logged in as Login
Guest
snewsgnewsmessagegeneralfactioninventorycombatroom
[Message Centre] :: [RPG Centre] :: [Question Centre] :: [White Scenarios] Archives » Bug base etiquette..
Year 13 Day 281 6:58 Bug base etiquette..
Janryann Sunnar

Not sure if it can be done, but I posted in the bug base and it was confirmed, but nothing more has been done. Can someone poke the base to see if there is feedback on my problem?

0002345

Thanks.


Year 13 Day 281 7:49 Bug base etiquette..
Kendall Holm

Patience

Your issue was confirmed but not assigned. Gav has it assigned now

edit: Not sure what etiquette has anything to do with this ;)

Edited By: Kendall Holm on Year 13 Day 281 7:50
____________


Year 13 Day 281 8:47 Bug base etiquette..
Vip Fortuna

For clarification, there are plenty of states a bug can have:

new - fresh report
acknowledged - means a tester has seen your bug report.
confirmed - means a tester has tested positively and confirms it is indeed a bug.
assigned - means a coder is assigned (has assigned himself) and is fixing it.
feedback - more / additional information is requested.
to be tested - coder (thinks he) has fixed the bug.
resolved - confirmation that the bug is fixed.
closed


I hope that clears your question on bug-base- ettiquette.

____________