Child pages
  • Reporting Samigo Bugs in Jira
Skip to end of metadata
Go to start of metadata

Before reporting a bug in JIra, always search Jira to verify that the issue has not already been reported. Once you determine that there's no Jira ticket that describes your problem, create a new Jira as described below:
 

  1. Log in to Jira
      
  2. Click Create Issue (below the Search box at the upper right). 
     
  3. In the Create Issue pop-up, set the Project to Samigo and Issue Type to Bug.  Then click Create.

     
  4. Fill out the Create Issue form, focusing on the following fields:
    • Summary: a short (10 words or less) description of the problem (e.g., Authoring Matrix / Clicking Save triggers new error reports)
    • Priority: relative severity of the problem.  Choose one of the following options:
    • Components: The functional areas of the tool affected by the bug. More than one component can be added.  If none of the component options fits, select Global.
    • Affects Versions: The version Samigo affected by the bug.  For the test fest, choose 2.9 Tentative under Unreleased Versions.
    • Assignee: Leave at default value of Automatic.
    • Environment:  information about the specific computer and server on which the testing occurred, including the following:
      • Desktop or laptop OS and version (e.g., win xp sp2)
      • Browser name and version (e.g., IE 8.x or Firefox 8)
      • URL of the server you are testing on (e.g., http://qa3-us.sakaiproject.org:8086/portal)
      • Tag/version number: this can be found in the last line of the footer (e.g.,  tags/sakai-2.9.0-a01 QA on Oracle - Built: 10/26/11 12:00 - Sakai tags/sakai-2.9.0-a01 (Kernel 1.3.0-a01)- Server qa3-us)
    • Description: a longer description of the problem and the site ID in which the problem occurred. Be sure to include step by step instructions for reproducing the bug.  
    • Attachments: It's also helpful to attach screenshots or screencasts to illustrate your description.  Please use jpg or png file format as thumbnail images of these display in the issues.
       
  5. Leave the remaining fields blank and click Create to submit.
     
  6. You will receive an immediate e-mail notification, as well as notifications whenever the issue is updated.  Please read these notifications, as the developer may need more information about the problem. To reply to a developer question or comment, click the link in the notification message to open the problem in Jira. Then click Comment to respond.  Do not try to reply to a Jira via regular email. Your message will bounce.
  • No labels