Skip to main content

Image Annotation for Marking Bugs with JIRA

Overview

Image annotation is a crucial feature for the “Mark as Bug” functionality in software development and quality assurance. This feature allows users to capture and annotate screenshots or images that showcase a specific issue or bug in the software application. The annotated images can then be easily shared with the development team, providing them with valuable visual information to help identify and resolve the problem more efficiently.

Step 1: After successfully running a test case, you can click on “Mark as Bug,”  select the relevant test case, and click to open the integrated bug reporting tool, such as Jira, to log the issue and initiate the bug-fixing process.

Step 2: Click the “Edit” button on the interface to open the annotation tools and customize the screenshot with your desired markups and annotations.

Step 3: Annotate and Edit the Screenshot

The interface provides a wide range of annotation tools to help you highlight and explain specific areas of the screenshot, including:

  • Highlight marker
  • Ellipse frame marker
  • Text marker
  • Callout marker
  • Caption frame marker
  • Curve marker

You can use these tools to add detailed annotations and draw attention to important sections of the image. The interface also includes editing controls such as Undo, Redo, and Delete, allowing you to easily refine or modify annotations as needed.

Step 4: Submit the Bug to JIRA

After annotating the screenshot using the available tools, submit the bug or issue to JIRA by filling in the required fields:

  • Issue Type
  • Summary
  • Description
  • Priority

Once the submission is completed successfully, a confirmation pop-up will appear, indicating that your bug report has been successfully integrated with JIRA.


Overall, TestGrid’s Image Annotation feature for the Mark as Bug functionality enhances the quality assurance and software development processes by providing a user-friendly and visually driven approach to reporting and addressing software issues.

Table of Contents