Changes between Version 73 and Version 74 of BugReportingGuidelines


Ignore:
Timestamp:
11/10/14 13:08:00 (7 years ago)
Author:
knowing42
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReportingGuidelines

    v73 v74  
    1111
    1212== How to report a bug or request a feature ==
     13
     14For GCI students:
     15
     16We 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 * See the list of projects [http://sunflower.sahanafoundation.org/eden/project/project?sector.name=None,Project Sunflower Projects]
     19 * Add the task under the relevant project and add the tag "bug" along with other tags.
     20
     21Bug reporting guidelines:
     22 * Please check to see if the bug you've found has already been reported.
     23 * Please provide full details to reproduce the problem, like the example below.
     24 * Be clear on which system your test is run against - e.g. http://demo.eden.sahanafoundation.org.
     25 * 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.)
     26 * '''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)
     27 * If the bug is relatively simple to resolve, please add the tag "easy", so it will appear on sunflower.
     28
     29Others:
     30
    1331We use Trac to manage bugs and feature requests.
    1432 * Before reporting or updating bugs, first [/register register for an account] and log in. (No approval is needed.)