Projects using internal issue module for Issue (Bug) Tracking

Note

This document is applicable only when your project is not configured with external issue tracker.

The Issue module enables internal issue management. You can create, view, and modify issues within . You can also add custom fields to tailor issue details to business needs.

You can:

  • View, add, modify, and delete issues

  • Manage the Issue Grid by displaying or hiding fields

  • Create custom fields and update system-defined values

  • Perform bulk operations

  • Configure email notifications for various triggers

  • Access issues logged during test execution directly in the Issue module

Note

When linking an internal issue from the Execution screen, the issue opens in read-only mode if users click on the link.

View and Organize Issue Details

Click the Issue Entity Key in the grid view to open the issue detail page.

Customize the grid view by resizing columns, organizing tabs, or applying filters and sorting. To learn more, refer to Manage Grid Columns.

You can view issue details from:

A. Individual Section Tabs

B. Combined View (Read Only View)

QPro_TS_Details_View.png

Details

In the Details tab, edit the following fields:

  • Summary: View the summary of the Issue.

  • Priority: Assign priority to the issue by selecting appropriate option from the drop-down. It is a mandatory field.

  • Type: Assign a type to the issue e.g. Bug, New Feature. It is a mandatory field.

  • Status: When an issue is created, it has default status Open.

  • Owner: Use the Owner field to select the user to be assigned of the issue.

  • Associated Releases: Assign relevant release to the issue by selecting appropriate option from the drop-down.

  • Labels: Add respective tags as labels to filter or differentiate the issues.

  • Environment: Enter environment details in which the issue was found e.g., Chrome, Firefox, Production, Staging, etc.

  • Description: Enter the description for the issue. Description can be added either in Plain Text or Rich Text.

  • User Defined Fields: If UDFs are added for the Issues module, then they are displayed on the Create Issue and Issue Details screen.

Note

For Rich Text, the super admin must enable the rich text editor for project from General Settings under Project.

Execution Runs

Issues logged from the Test Executions module are displayed here.

View Archived Test Runs

Execution runs are archived when the associated Platform, Release, Cycle, or Test Suite is archived. When a test suite, platform or Release/Cycle is archived, the test executions associated with them will be hidden on the Execution Runs tab of the test case.

To view archived test runs, select the Show Test Runs with Archived Platform(s)/Release(s)/Cycle(s)/Test Suite(s) checkbox on the Test Executions tab.

View_Archived_Test_Runs3.png

Execution Time and Remaining Time

To view Execution Time and Remaining Time for test execution, open the issue detail page and go to the Execution Runs tab.

The columns Execution Time and Remaining Time are added to the grid in the following locations within the application:

  • In Test Executions tab under Test Suite detail page.

  • In Test Executions tab under Test Case detail page.

  • In Execution Runs tab under Issue detail page.

Execution Time of a Test Suite: Calculated based on the estimated time of all test cases within the suite.

Remaining Time of a Test Suite: Calculated for all "Not Run" test cases after execution. Test cases marked as "Failed" or "Blocked" are also considered as having remaining work. The Remaining Time is adjusted for test cases with "Pass" and "Not Applicable" statuses.“Not Applicable” status accordingly.

Example 15. Calculating Execution Time and Remaining Time.

Execution time

Status

Remaining time

TC1

2

Pass

-

TC2

3

Not Applicable

-

TC3

4

Failed

4

TC4

5

Blocked

5

14

9



Requirements

The requirement tab helps link single or multiple requirements to an issue through the Requirements tab on the Issue details page.

To ilnk a requirement, perform the following steps:

  1. Open the Issue details page.

  2. Go to the Requirements tab.

  3. Click Link.

  4. Use filters such as Labels and Folder paths to refine the list (if needed).

  5. Select the requirements from one project and click Link.

  6. Select another project from the Project drop down. Select the requirements from that project.

  7. Click Link and Close.

QPro_IS_Link_Requirements_to_Issue.png

View Linked Requirements

The system links the selected requirements to the issue, and the linked records are displayed on the screen.

The linked requirements are displayed on the screen. If a requirement belongs to another project, its Entity Key is shown. Clicking the Entity Key opens the requirement in that project and switches you from the current project.

Link Requirements By Entity Key

This feature allows users to link the latest version of a requirement to an issue by using the requirement key, with multiple keys separated by commas.

Note

Notes:

  • A maximum of 500 entities can be linked at a time.

  • The system ignores the requirement key if a relevant requirement with given key is not found.

  • If a single key is mentioned multiple times, it will be linked only once.

  • If an older version of a requirement is already linked, linking the same requirement key does not replace it. The latest version is skipped.

  • The system only links the latest unarchived version of requirements.

To link requirements using Entity key, perform the following steps:

  1. Go to the Requirements tab in the Issue Detail view.

  2. Click Link.

  3. Use filters to search for and select the required requirements.

  4. Click Link or Link and Close.

Unlink Requirements

To unlink requirements, follow these steps:

QPro_IS_Unlink_Requirements.png

  1. Go to the Requirements tab of the issue.

  2. To unlink a single requirement, click the Unlink icon for the requirement. The requirement is unlinked after confirmation.

  3. To unlink multiple requirements, select the requirements to unlink and click Unlink Selected.

Attachments

View, download, add, and delete attachments. Refer to Managing Attachments to know more.

Change Log

Note

This tab is visible if the Audit and Compliance package is enabled for the .

The Change Log tab shows changes done in the particular entity like the activity log. To know more about change log, refer Change Log document.

Comments

You can view, add, edit, and delete comments in . Refer to Add Comments to know more.

Combined View

The tab displays a read-only version of the details page, showing all sections on a single page. The information is viewable but cannot be edited.

Add Issues, Bugs or Defects

To add issues, perform these steps:

  1. Open the Issue module.

  2. Click New.

  3. The Create Issues screen opens.

  4. Fill the issue details.

    Table 23. Steps to log issue from Issue Module

    Summary

    Add the summary of the Issue.

    Priority

    Assign priority to the issue by selecting an option from the drop-down. It is a mandatory field.

    Type

    Assign a type to the issue e.g. Bug, New Feature. It is a mandatory field.

    Status

    When an issue is created, it has the default status Open. Assign appropriate status from the drop down.

    Owner

    Use the Owner field to select the assignee of the issue.

    Associated Releases

    Assign relevant releases to the issue.

    Labels

    Add respective tags as labels to filter or differentiate the issues.

    Environment

    Enter environment details in which the issue was found e.g., Chrome, Firefox, Production, Staging, etc.

    User Defined Fields

    UDFs added for the Issues module are displayed on the Create Issue and Issue Details screen.

    Description

    Enter a description for the issue. Description can be added either in Plain Text or Rich Text.



Note

To enable rich text editor, the Enable Rich Text parameter should be enabled for the Project. Refer to Enable Rich Text Editor for more details.

QPro_IS_Log_issue_from_Issue_Module.png

Note

  • The supported file formats to upload are jpg, jpeg, png, and gif.

  • The maximum file size should be 1 MB (for images uploaded through browsing).

  • Paste the html or xml content into the Source editor of the "Large Text" field type and it auto-renders the code to show the text outputs on the screen.

Link Attachments: Link attachments while creating issues. Refer to Managing Attachments for more details.

Edit Issues

Use an inline editor to edit issue details.

Manage Issue Status

Update the status of an issue using system-defined options such as Open, Re-opened, Resolved, and Closed. To configure more status go to the Manage Fields section.

The Status field under Manage Fields tracks issue workflow and progress. List values for this field can be edited or updated in Lists.

Steps to log issue from Execution screen of Test Suites Module

Log issues at test case as well as test step level. Open the Execution screen and click the bug icon for test case or test step.

Note

Archiving assets is not supported in the Issue Module.

Deleting Issues

Delete issues from the grid or from the detail page.

  • To delete an issue from the Details tab, click the Delete icon.

  • To delete an issue from List View, click the Cog icon and select Delete.

  • To delete issues in Bulk, open Bulk Operations and select Delete.

Manage Issue View

Refer to see Issue view.

Sharing Test Assets with Other Users

Share requirement summary and details with other users via different channels.

Share Requirement

QPro_RQ_TC_Sharing_Assets.png

To share a requirement via email, perform the following steps:

  1. Open the requirement details page.

  2. Click the Share icon.

  3. Enter the email addresses.

  4. Write a message (optional but recommended).

  5. Click Share.

Get Requirement Link

To copy requirement link directly, perform the following steps:

  1. Open the requirement details page.

  2. Locate and click Copy Link icon on the breadcrumb navigation.

  3. Share this link via any preferred communication channel.

    QPro_RQ_Share_Asset.png
Example 16. URL Syntax

https://<URL>/#/<AssetType>/<AssetKey>;



Authorized members can access the asset directly via the shared link.

Add new custom fields, add new values to system-defined fields

Add custom fields and new values to system fields from Manage Fields.

Set e-mail Notifications for multiple triggers

Set email Notifications for multiple triggers.

Log Issues, Bugs, Defects from Execution Screen

Refer to Adding/Linking Issues to Test Case and Test Step for more details.

Import Issues

Importing Issues from Excel File

Export Issues

Exporting Issues to CSV Format /XLSX Format

Create Requirement from Issue

To create a requirement from an issue:

  1. Select the issue and add a new requirement.

  2. The new requirement copies common field values and use the same name, which can be edited.

The original issue is linked to the new requirement. On the Issue details page, the Requirements tab shows this new requirement, and on the Requirement details page, the Issues section shows the originating issue. Only users with "Create" rights for Requirements can perform this action.

Steps

Follow either of the ways:

  • Select an issue on grid pane and click Add on the toolbar.

  • Point to From Issue and select Requirement.

  • Right click an issue on the grid pane, point to From Issue and select Requirement.

Email Issue Details to Other Users

Send issue details to and external users. The details include system fields, and attachments.

Internal Tracker: Attachments are sent in a zip file (up to 25 MB) if using a internal issue tracker.

To email issue details to users, perform these steps:

  1. Open the issue details page.

  2. Click the email icon.

  3. Enter recipient email addresses (separated by commas) and send the email.a and send it as an email.

In this section:
© 2025
Publication date: