In Worksoft SaaS, "Issue Store" helps you in storing the "issues" for the failures or any errors and store those issues using the "Issue Store" locally in the Worksoft SaaS application. Worksoft SaaS allows you to create & view the reported issues, link/delink the issues to a specific Test Run. (or) Test Cycle (or) to all the recent Test Runs available in the Test Runs Home screen.

This is a very powerful feature that provides you can store the issues locally which along with the creation of the local issues gives you insights about this information in the Analytics Reports.
To know more about this Consolidated Triage Report, click here.

You can also view the auto triage of the local issues based on the past history of the issues that are created locally for the failed tests in the Worksoft SaaS application (to be supported in the future.)

A bug icon is available next to the "Annotations" icon in the Execution Results page will allow you to create the issues. Upon clicking this icon, it will display the list of options available in the popover.

You can also Create/Search/Link/Delink/Comment an issue for a Test Run directly from the Test Runs Home page.

Create an Issue

Once you click on the 'Create a New Issue' icon, a popup would be displayed with the list of fields that allows you to create the issues locally.

You have executed a batch and triaged the failures. You conclude that there is an issue with the Application Under Test (AUT) and want to create an issue locally. You click on the corresponding icon or label (first one) in the pull-down to start creating the issue. Worksoft SaaS shows a popover with all the required fields.

Once you enter the required fields in the popup about the issue, you can save the issue locally by clicking on the "Create & Exit" button.

• Issue Summary and Description: Under this section, you have two fields where you can enter the 'Summary' and 'Description' in the respective fields, later not being mandatory.
• Linkage to failed Test Runs: Under this section, you can link the current issue by using the available list of options and selecting the specific testing context from the dropdown.
1. Current Run Definition within current Test Cycle only: On selecting this option, all the failed tests of the particular Run Definition tagged to the Test Cycle will be displayed in the 'Link this issue to other Test Runs' dropdown.
2. Current Test Cycle only: On selecting this option, all the failed tests tagged to the Test Cycle will be displayed in the 'Link this issue to other Test Runs' dropdown.
3. 1000 Recent Test Runs: On selecting this option, all the failed tests from the recent 1000 test runs will be displayed in the 'Link this issue to other Test Runs' dropdown.

View Reported Issue(s)

You can view/search the reported issues that are linked to a Test Run in two ways.

1. You can directly click on the “Issue Store” option from the “More” dropdown which will automatically redirect to the Test Runs Home with the “Search Issues linked to Test runs” popup.
   

   

   You can see a popup(shown below) where the first option "Show Issues Reported From:" is disabled with "This Project" as you can perform the search pertained to this project only. You can also see the first radio button "The Test Cycle linked to this Test Run only" is disabled under the second option "Test Cycle(s) to include:" as you are not searching the Issues by selecting a specific test run id.

   
   

   For the filtered issues, you can see the issues which are differentiated by the icon for the issues that are either assigned manually or by Worksoft AI/ML. By just clicking on the icon, you can see the information about the date-time when the issue is assigned to the test run along with the issue previously assigned to the test run's information.

2. You can also perform the search by clicking on the "View Reported Issue(s)" from the pull-down. If one or more issues are linked to the Test Run, you will see the number of issues in the text. For example, if 2 issues are linked the text would show "View 2 Reported Issue(s)". When you click on the icon, you will see a popover with the following fields to help search for the issues linked.

You can perform a search for the issues reported locally by selecting the 'Local Issues in Worksoft SaaS' radio button. This button is selected by default.

1. Shown only issues reported from: You can choose to search for linked issues on the test run alone or all Test Runs pertaining to the same Run Definition and same Testing Context or same Run Definition and different Testing Contexts. You will find this option handy if you want to avoid creating or linking duplicate issues.
   
2. Test Cycle(s) to include: You can either select the specific test cycle tagged to this test run or any of the available test cycles that the test run is part of.
   
3. Date of the test execution: If you have multiple Jira usage contexts, you can select one or more of them from the dropdown.
   
4. Date of the issue reporting into Jira: You can select the execution date range and when the issues are logged into Jira if needed.

You can also perform actions like adding the annotations or editing the filtered issues by performing the search by selecting the "Issue Store" from the "More" dropdown or from the "View Reported Issue(s)" from the options as shown below.

Link an Issue

You have triaged a failed Test Run and now ready to create an issue locally for the AUT. But you have already created a ticket for a similar issue (could be that the same functional issue has shown up in another browser of test run) and don't want to end up creating duplicate issues. In that case, you can use the "Link an Issue" feature.

Use the "Link an Issue" icon or label to bring up the popover that can be used for linking an issue. Once you select the radio button as "Worksoft SaaS", you can see the 'Search Issues' dropdown which fetches all the local issues and the checkbox for adding the annotations while linking the issues (selected by default). You will be able to select one or more of the issues to link to the test run.

Delink an Issue

You have previously linked one or more local issues to a test run. And subsequent executions fo the same Test has shown that the issue (in AUT) no longer exists. This could've either resulted because of some flakiness or fixes in the AUT. In such cases, linking the issue(s) with the Test Run may not be relevant and you choose to delink the issue.

On clicking the "Delink an Issue" icon or label, you can see all the local issues linked to the respective test run in the dropdown. You can either select one or more of them and delink those by clicking on the "Delink" button.

When you click on the 'Delink' option, you see a confirmation prompt is displayed. 

Add a Comment to an Issue

You add the comments to the locally created issues by selecting the issue keys from the dropdown by selecting the "View & Assign Annotation(s)" label from the "More" dropdown.in the Test Runs Home page.

You can add the comments to the issues that are created in Jira for the failures found in the Application Under Test (AUT) and you wish to add notes/comments/links to the issue whenever there is an update available for the respective issue. In such a scenario, you can use the "Add a Comment to an Issue" feature.

On clicking the "Add a Comment to an Issue" icon or label, you can select a specific Jira Usage Context. associated Projects and the specific Issue Key from the dropdown to which you wish to add the comments. Once you save these comments, you can view/modify them in the Jira application.

For example, you have executed tests on a Test Cycle and have found an issue and created the issue locally which is in the "Open" status. The other two different statuses are available for locally created issues. You can move from one status to another by performing the search and editing the respective issue as shown below:

• Open: By default, when you create an issue locally, it is in the "Open" status.
• Close: You have seen that the issue which was created earlier doesn't exist anymore and you can change the status of the issue as "Close".
• Reopen: The issue which was moved to "Close" status can be re-opened, if you see that the issue replicates after any deployments to the application.

If you have Jira integration already?

On having the Jira application integrated into Worksoft SaaS, you can have the locally created issues that can also be created into the Jira.