Log in to remove this sponsored message
NeoCRS Bug Report Guidelines
Version 0.1 [Revision: 3 April 2009]
guideline.index- Overview
- Titling Threads
- Report Content
- Bug Statuses
- Thread Retention
- Further Information
_____________________________________________
guideline.overviewThis forum has been here for some time, and with CRS expanding, it seems like the right thing to do is create the guidelines for bugs relating to CRS. This forum is essentially for all bugs relating to the Contribution System. This includes NeoCRS and general contributions to Profiles.
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 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 investigating of bugs so it's important you provide all of this initially.
Below are some detailed guidelines of the type of content that should be submitted within a bug report to ensure it can be looked into in the fastest time possible.
titling.threadsThe first thing an administrator will see when he/she browses 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:
"[ Bug ] Concept Art Uploader is Broken"
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:
"bug found needs fixing!!!"
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.
report.contentbug.statusesEach thread, after having been created and acknowledged by 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.
Closed
Whilst bugs can be resolved, it's always better to test them. So if you see the status of a thread as being 'Closed' it will mean that it has been fixed, and other members have been unable to reproduce this bug. 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 the portals, 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.
CRITICAL
This status is assigned on top of one of the aforementioned statuses. This status is used only to identify bugs that need to be fixed immediately for whatever reason, as this will push the bug to the top of the admin's list. Generally this will be assigned to major security or display issues.
thread.retentionWhen bug reports are flagged as 'closed', they will usually be closed and kept as an archive, in case of repetitions of the bug. If you notice a bug that has been flagged as 'closed', 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.
further.informationAny questions about bug report submissions can be directed to the following inboxes - Intoxication, ar_cat. They'll try to get back to you ASAP and hopefully be able to answer any queries you have.
If you would like threads to be reopened, please send a PM to ar_cat.
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!
Regards,
The NeoCRS Teamneoseeker.comAdapted from NeoWiki Bug Reporting Guidelines, by Krunal.Mod Edit: Jul 23, 12 9:48pm by Intoxication