Report bugs in test cases from Zoho QEngine with Jira | Zoho QEngine Help

Reporting bugs in test cases from Zoho QEngine with Jira

What does this page cover

Learn how to report bugs from test case executions using the Jira integration. Before you begin, it's essential to understand how the Jira integration works and its configuration.

Availability 

  1. This feature is available on all Zoho QEngine plans for the web, iOS, Android, and API platforms.
  2. Super admins, admins, managers and testers can report bugs to Jira from a test case execution and view the status of a reported bug.

1. Steps to report a bug

NotesNote: Before you can report bugs, a super admin must set up the Jira integration and associate your Zoho QEngine project with a Jira project. Refer to Configuring Jira in Zoho QEngine

Using the Jira integration, you can report bugs from test case executions in Zoho QEngine. You can either create a new issue in Jira or link the execution to an issue that already exists in Jira

1.1 Create a new bug

NotesNote: To report a bug, you must have access to the associated Jira project.
  1. Navigate to your preferred project. From the Results tab, open the required test plan's results.
  2. Click the Bug icon {} on the required test case. A bug can be reported irrespective of whether a test case passed or failed.



  3. Review the auto-filled description in the Report a Bug panel. This is pre-filled with execution details, which you can edit if you need to add additional context:



    1. Work Type: Choose the correct type (e.g., Story, Task, and Bug).
    2. Item Name: Pre-filled with the test case name, but can be edited if needed.
    3. Description: Pre-filled with execution details such as the test case name, environment configuration, failure log (for failed runs), whether it was run on the local agent or using Zoho Cloud, the test case version, and the start time. You can edit the content if additional context is required.
    4. Attachments: Screenshots captured during the test execution are attached automatically, including a screenshot of the failed step when applicable. Click the + icon to attach additional files, up to 10 per bug.
    5. Assigned To: The field is assigned by default to the user who reported the bug. You can change the assignee if needed. Click Create to submit the bug.

Alternatively, you can also report bugs from the test case summary page within the execution results.



Notes

Note:

  1. A bug can be reported for each test case execution in test plans, so multiple bugs can be logged for the same test case across different executions.
  2. If a test case is re-run after failure, you can also report a bug from its re-run execution results page.
  3. You can't link a test case execution to an existing Jira issue. Each report creates a new issue in Jira.

If the issue for this test case execution has already been reported, you can link the execution to the existing issue instead of creating a new one, to avoid duplication.

  1. Select Link to a Bug from Item Type in the Report a Bug panel.



  2. Choose the relevant Jira issue under Select Item.
  3. Attach any required files and add comments, if needed.
  4. Click Link to associate your test case execution with the existing issue.

2. Preview test cases with bugs

Now that you've learned how to report a bug, let's see how to view the status of a reported bug from the test plan listing page or from a test case's summary page.

  1. Navigate to your preferred project, then open the required test plan's results from the Results tab. Test cases with reported bugs are marked with a red bug icon.
  2. Click the Bug icon {} on the required test case to open the Bug Summary card.

The card shows the reported Jira issue's name, item type, associated sprint, and who it's assigned to, along with its current status.

NotesNote: Only users who have access to the associated Jira project can view the status of the reported bugs.
  1. Click the link at the bottom of the card to open the issue directly in Jira.

The card's status auto-syncs with Jira each time you open it. So if you resolve the bug in Jira, the status on the card updates to match the next time you check it.

Notes

Note:

  1. If you remove the project's association with Jira, the bug status is no longer visible in Zoho QEngine, though it remains accessible in Jira. The bug status is also no longer visible in Zoho QEngine if the reported bug is deleted from Jira or your Jira account permissions change.
  2. You can also remove the linked bug from this panel. Clicking the remove icon {} dissociates the bug and the test case.

Alternatively, you can also view a reported bug's status from a test case's summary page.

NotesNote: You can't preview reported bugs for a test case run through live preview. It only works from a test case's summary page for a test plan execution.
  1. Navigate to your preferred project, then open the required test plan's results from the Results tab.
  2. Click the required test case in the listing page to open its summary page.
  3. Click the Bug icon to open the Bug Summary card.

3. Related links

  1. Integrating Zoho QEngine with Jira
  2. Configuring and managing Jira in Zoho QEngine
  3. Results

4. What's next

Next step
Previous step
Next step

Now, that you've learned how to report bugs, see how to review your test cases' overall performance in Results.

Previous step

Before reporting bugs, learn how to configure the integration with Jira and associate your Zoho QEngine projects with Jira projects