You can configure a Qualitia project to create a defect for a test case iteration report. You need to integrate a Qualitia project with one of the following defect management systems: 

• Jira
• TFS/Azure DevOps.

Quaitia automatically logs the defects for a test case iteration report whose executions status is Defect. However, in certain conditions where auto-logging of defects are not possible, then you need to log the defects manually.

For more information, refer to Conditions for Auto-Logging of Defects.

Configuring a Qualitia Project with a Defect Management System Project

You can integrate a Qualitia project to a Jira or TFS/DevOps project for managing defects. 

You can use the Auto-Mode option to enable or disable auto-logging of defects. You can log defects manually even if the auto-log mode is disabled.

To configure a Qualitia Project with a defect management system:

1. Do one of the following to access the Project Settings dialog box.
   1. Go to Admin >Project, under the Configuration column, click Configure next to a project.
   2. Go to Settings > Project Settings. 
      A list of existing Qualitia projects appear.
2. Click the Defects tab.
3. Do one of the following:
   • Click the Jira tab to integrate with Jira for logging the defects.
   • Click the TFS tab to integrate with TFS/Azure DevOps project for logging the defects.  
4. Perform this step only if you want to integrate with a Jira project.
   • Jira URL: Lets you specify the Jira Server URL to which you want to connect for logging the defects.
   • User Id: Lets you specify your Jira User Id to connect with the Jira Project
   • Password: Lets you specify your Jira password to authenticate the Jira Project.
     Note: If you do not enter a Jira User id and password, then Qualitia uses the credentials of the first user who had configured the Qualitia project with the selected Jira Project.
   • Connect: Click to get the available Jira projects.
   • Jira Project: Lets you select the Jira project from the drop-down list to which you want to integrate the current project defects.
5. Perform this step only if you want to integrate with a TFS/ Azure DevOps project. 

   • Server URL: Lets you specify the TFS/Azure DevOps URL.

   • PAT: Lets you specify the unique Personal Access Token (PAT) provided by Microsoft Azure DevOps.

   • Get Projects: Click this button to display the list of all the available projects in TFS/Azure DevOps Server

   • Project: Lets you select a project to which you want to integrate.

6. Enable Auto-Log Mode to allow Qualitia to auto-log the defects.
7. Under Mandatory Defects Fields, select or enter the default values in the mandatory fields that are automatically displayed, which are used to auto-log the defects.
   For example, if you are integrating with a Jira project, which defines that severity and priority are mandatory, then this dialog box displays these two fields. You need to enter the default values in these fields.
8. Click Save to save the settings.

Conditions for Auto-Logging of Defects

The auto-logging of defects occurs only for the test case iteration reports whose execution status is Defect. 

For auto-logging of defects, you must ensure to do the following: 

• Enable the Auto-Log mode in the Defects tab of Project Settings dialog box.
• Ensure the test suite execution results are pushed to Real Time reporting portal. For more information, refer to Pre-Requisites for Real Time Reporting Portal.

Logging a Manual Defect from a Test Case Iteration Report

The following table shows the scenarios where logging of defects manually can be used as an alternative to auto-logging of defects. 

To log a manual defect in the integrated defect management system:

1. Login to Reports and Dashboard Portal.
2. Click Real Time Reporting Portal.
3. From the Suites of Suites screen, open the test execution in which you want to create a defect.

4. From the Test Suite Execution Summary Report, open the Test case, and then click the test case iteration for which you want to create a defect.
   Note: The status of test case iteration must not be Not Executed.

5. Click the three dots menu present on the right side of the page and select Log JIRA defect or Log TFS defect.
   (Depending on the Defect management system you have integrated with Qualitia Project)

6. Do the following in the order listed:

   1. The Defect Title is automatically generated in the format as Suite Name – Test Case Name – Test Case Iteration Number.
      You can edit this field.

   2. Enter the required information associated with the defect, in Defect Description.
      The default content for this field automatically displays environment details such as browser name, which you can edit.

   3. Under Mandatory Defects Fields, select or enter the default values for the mandatory fields.
      As per the settings defined in the project of the selected Defect Management System, the mandatory fields are displayed automatically.  
      For example, if a Jira project to which you want to integrate defines that severity and priority fields are mandatory, then this dialog box displays severity and priority under Mandatory Fields.
7. Click Submit.
   A notification message with the defect Id and its URL is displayed.
8. Click the Defect URL to view this defect in the associated defect management system. 
   The defect created in the associated defect management system project shows the link to the test case iteration of the test suite.

Viewing Defects in Real Time Reporting Portal 

Open the test suite execution report in which a defect is created automatically or manually. Under the Status column, upon hovering on a test case iteration report, all the associated defect Ids along with their links are displayed. Also, you can know whether the defect is automatically created or not.

Viewing Defects in the Selected Defects Management System

The issue created in the selected defect management system contains the following details: 

• For defects that are automatically logged, the descriptions contain the details such as Machine Name, Operating system used, and Browser name along with its version.
• When a defect is created, its default name is generated as Test Case Iteration number - Test Case name - Suite Name.
• After a defect is created, the defect contains a link to view the test case iteration report in Real Time Reporting Portal.