Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section
Column

Make sure the bug hasn't already been reported by searching through pre-existing JIRA issues. If the bug has been reported, you can add a comment to the existing issue (if you think the specific context in which you encountered the bug is useful to developers, or if you think the bug should be a higher priority. If the bug hasn't been reported, make a new JIRA issue.)

Column
width30%
Info
titleUseful JIRA guides

Using Quick Search

Report content

Section
Column

A bug report should include: 

  • Your operating system and browser, including versions.
  • A summary of the issue. 
  • The steps developers should take to reproduce the bug. Be as explicit as possible, and assume the reader has never used the tool before. 
  • The results you expect to see in the absence of the bug. 
  • What actually happens if you take the steps to reproduce. 
  • The URL of the page where you're encountering the bug. You should copy and paste this from your browser's address bar. 
  • Any screencaps or videos as needed. This is especially important for visual issues or animation issues. 

To keep things organized, you can copy and paste the template below into the ticket text: 

Code Block
*Operating System and Browser:* 
 
*Summary:*
 
*Steps to Reproduce:* 
 
*Expected Result:* 
 
*Actual Result:* 
 
*URL:*
 

Make sure your new ticket is in the "Mandala United" project. You should also add the appropriate "Component" (usually the tool name) to your bug. Here's an example of the report form: 

 

 

Column
width30%
Info
titleUseful JIRA guides

Creating an Issue

Attaching Files and Screencaps

Info
titleMaking screencaps and screencasts

Take a screenshot on your Mac

Record your screen using QuickTime Player (Mac)

Take a screenshot on Windows

Screen recording software for Windows

 

 

 

...

Section
Column

Make sure the bug hasn't already been reported by searching through pre-existing JIRA tickets. If the bug has been reported, you can add a comment to the existing issue (if you think the specific context in which you encountered the bug is useful to developers, or if you think the bug should be a higher priority. If the bug hasn't been reported, make a new JIRA ticket.)

Column
width30%
Info
titleUseful JIRA guides

Linking Issues

You should link your new bug to the original testing request JIRA issue, if one exists. This helps people see all the bugs that resulted from that test at once. 

...