Changes between Version 75 and Version 76 of BugReportingGuidelines


Ignore:
Timestamp:
11/11/14 11:47:34 (7 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReportingGuidelines

    v75 v76  
    1111
    1212== How to report a bug or request a feature ==
    13 
    14 For GCI students:
    15 
    16 We will be using [http://sunflower.sahanafoundation.org/eden/default/index Sunflower], Sahana's Community Management portal for reporting bugs.
    17  * Before reporting or updating bugs, first [http://sunflower.sahanafoundation.org/eden/default/user/register Register for an account] and log in. (No approval is needed.)
    18  * [http://sunflower.sahanafoundation.org/eden/project/task/create?bug=1 Report a Bug]
    19 
    20 Bug reporting guidelines:
    21  * Please check to see if the bug you've found has already been reported.
    22  * Please provide full details to reproduce the problem, like the example below.
    23  * Be clear on which system your test is run against - e.g. http://demo.eden.sahanafoundation.org.
    24  * You may also wish to check the [https://github.com/flavour/eden/commits/master Commit Logs] to see if the bug is being fixed. (Note to bug fixers -- please accept the bug on sunflower and say you're working on it.)
    25  * '''Screenshots''' are good for showing the main problem screen if hard to explain, however, if you get a ticket, then simply the ticket ID would be better than a screenshot, as can simply copy/paste to find the relevant ticket)
    26  * If the bug is relatively simple to resolve, please add the tag "easy", so it will appear on sunflower.
    27 
    28 Others:
    29 
    3013We use Trac to manage bugs and feature requests.
    3114 * Before reporting or updating bugs, first [/register register for an account] and log in. (No approval is needed.)
     
    4326 * '''Screenshots''' are good for showing the main problem screen if hard to explain, however, if you get a ticket, then simply the ticket ID would be better than a screenshot, as can simply copy/paste to find the relevant ticket)
    4427 * If the bug is relatively simple to resolve, please add the keywork  "easy", so it will appear on the [http://eden.sahanafoundation.org/report/18 Easy Bugs for Beginners] Report.
     28
     29=== For GCI students ===
     30We will be using [http://sunflower.sahanafoundation.org/eden/default/index Sunflower], Sahana's Community Management portal for reporting bugs.
     31 * Before reporting or updating bugs, first [http://sunflower.sahanafoundation.org/eden/default/user/register Register for an account] and log in. (No approval is needed.)
     32 * [http://sunflower.sahanafoundation.org/eden/project/task/create?bug=1 Report a Bug]
     33
     34Bug reporting guidelines:
     35 * Please check to see if the bug you've found has already been reported.
     36 * Please provide full details to reproduce the problem, like the example below.
     37 * Be clear on which system your test is run against - e.g. http://demo.eden.sahanafoundation.org.
     38 * You may also wish to check the [https://github.com/flavour/eden/commits/master Commit Logs] to see if the bug is being fixed. (Note to bug fixers -- please accept the bug on sunflower and say you're working on it.)
     39 * '''Screenshots''' are good for showing the main problem screen if hard to explain, however, if you get a ticket, then simply the ticket ID would be better than a screenshot, as can simply copy/paste to find the relevant ticket)
     40 * If the bug is relatively simple to resolve, please add the tag "easy", so it will appear on sunflower.
     41
    4542== What is a Bug? ==
    4643It is important to properly identify bugs as these need to be fixed in priority to implementing enhancements. Sometimes it may not be clear if issues you encounter are in fact bugs. The following ARE bugs: