GameGrep Bug Reporting Guidelines

Forum Options:	my.neoforum register members prefs search faq

Options: Print subscribe remove send to friend NeoPM Topic: GameGrep Bug Reporting Guidelines
Threads List « Next Newest Next Oldest »
teodortenchev AWAY till 26th September! Neo or Bust total posts: 7585 neopoints: 9404 GameGrep pts: 1014 since: Apr 2003	Apr 13, 07 at 09:27AM GameGrep Bug Reporting Guidelines
	GameGrep Bug Reporting Guidelines Version 0.3 [Revision: 13th April 2007] guideline.index Overview Titling Threads Report Content Bug Statuses Thread Retention _____________________________________________ guideline.overview This forum has been set up to allow users to bring to the attention of the administration bugs, glitches or errors in the any aspect of GameGrep's coding which may be reducing the functionality of the service or causing other issues. The main thing to note when reporting a bug in this forum is to ensure that you provide as much information as possible so that it can be quickly reproduced by an administrator and fixed; detailed recreation steps, as well as information such as what browser you are using and so forth, can assist greatly in the investigation of bugs so it's important you provide all of this initially. Below are some detailed guidelines on the type of content that should be submitted within a bug report to ensure it can be looked into in the fastest time possible. [ Return to Top ] titling.threads The first thing an administrator will see when they browse the forum is a list of thread titles. It is therefore important that when raising a bug report within this forum, your title gives viewers a general idea of what the content of the thread is going to be before they even open it. Thread titles such as this are a good example of what we're looking for here: "Unable to Attach a Primary Image to News Article" As you can see, that thread title basically sums the report up in a nutshell, thus giving viewers a general idea of what to expect in the report without having to open it. This is much more helpful than, for instance, using this as a thread title: "an annoying bug! :S" This tells anyone browsing the forum pretty much nothing about what they can expect in the report, which may slow down the investigation and fixing progress as well as causing people additional time having to browse through before having an idea of what's going on. [ Return to Top ] report.content The following should be made clear within your actual post: What the bug does/prevents you from doing. Detailed instructions on how to recreate the bug scenario. Screenshots if possible. What browser version and OS you are running. Any error messages that are being displayed to you. Below are two examples of correct bug reports. Example Report 1: quote Bug: Database error when trying to edit articles! What Happens: When I try to edit my news article I get a database error. Browser/OS: Mozilla Firefox 2.0.1, SuSE Linux 9.3 Professional Error Messages: MySQL Error: cannot connect to db ($password failed) Example Report 2: quote Bug: Cannot log in to GG What Happens: When I try and login, it refreshes the page without doing so. Browser/OS: Mozilla Firefox 2.0.1, Windows XP Home Error Messages: N/A Notes: I think this is a browser related problem. [ Return to Top ] bug.statuses Each thread, after created and acknowledged a moderator, will have a tag appended underneath the thread's title in this forum explaining the current status of the bug. The standard statuses that will be assigned and their meanings are as follows: Unconfirmed This status is initially assigned to bugs that have been logged if they appear to be legitimate reports, but have not yet been confirmed by another member. Confirmed This means that the bug has not yet been addressed by an administrator, but it has been confirmed as occurring by one or more reliable sources (or seen in action by the moderator reviewing). Fix Pending This status means that the bug has been acknowledged as occurring by an administrator and they have specified a set date or version release as to when it will be fixed. Resolved When bugs appear to be fully resolved and fixed, they will receive this status. If you notice bugs still occurring that are flagged as this, a moderator should be contacted and made aware so he/she can reopen the report. Redirected If a bug has already been reported in the past and already has a thread created for it, any new threads about the same bug will be redirected to the original. Bad Bugged This status is assigned if a member has posted a thread here whereby what they are describing is either no relation to a bug happening on GameGrep, or what they are describing cannot be confirmed as happening server-side, which would most likely mean they have problems within their own computer/browser's configuration. [ Return to Top ] thread.retention When bug reports are flagged as 'resolved', they will usually be set to automatically delete themselves after a 30 day period as, after which if no further occurrences are reported, they will likely no longer be needed. If you notice a bug that has been flagged as 'complete', yet you still believe is occurring in some form, please contact a moderator as soon as possible and make them aware of the situation so the thread can be reopened for further reports. [ Return to Top ] Thanks in advance for your cooperation and heeding these guidelines, which will hopefully ensure that any bugs that crop up and are ironed out as fast as possible!
	quote quick quote edit quick edit del report
Members, log in or register to remove these ads.
[All dates in (PT) time]	Threads List « Next Newest Next Oldest »