Skip to content

Create/Comment/Link/Delink/Search an Issue (locally & in Jira) in the Test Runs Home & Execution Details Tab

← Integrating your Issue Tracking System

Worksoft SaaS allows you to create issues locally & link/delink them to a specific Test Run (or) Test Cycle (or) to all the recent Test Runs available in the Test Runs Home screen and you do not need any Jira Usage Context(s) or any additional configurations for creating the issues locally.

A new icon is added in the Execution Results page that shows up by default (irrespective of Jira Integration is set up or not.) The icon is placed beside the name of the Run Definition/Scenario in the page.

.

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

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.

If the Jira Integration is already set up and you want the issues to be created in Jira along with the issues being created locally, you can select the checkbox 'Create this Issue in Jira as well', you can observe that the 'Create & Exit' button changed to 'Create & Continue' which upon clicking redirects to the Create an Issue in Jira popup and the linked issues count can be visually seen as the superscript to the Jira icon.


Create a New Issue


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.
  • 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.


Once you enter the required fields in the popup about the issue, you can save the issue locally or you can also have the issue created in Jira by selecting the "Create this Issue in Jira as well" checkbox. Once you select this checkbox, you can see the "Create & Exit" button changed to the "Create & Continue" button. After clicking on the "Create & Continue" button, you can select a specific Jira Usage Context, Worksoft SaaS will pull all the fields from your Jira Project.

If there are no Jira Usage Contexts(JUC's) created within the project, the checkbox will not be shown in the 'Create Issue' popup.

Please note that all Standard & Custom fields, configured in Jira Project, show up by default. You can create an issue once you fill all mandatory fields. The fist failed instruction screenshot is attached to the respective created issue and is also shown in Jira Application. If there are multiple failures within the test run and to have a specific instruction's screenshot to be linked to the issue(to be supported in the future).


Also, please note that the messages from the Jira application would be shown in the popup if there are any configuration issues while creating the issue(s) to the test run. For example, if you try to link an Epic to the Sub-Task, the below message would be displayed.


Add a Comment to an Issue


You have created the issues (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.

 

Link an Issue


You have triaged a failed Test Run and now ready to create an issue (locally/Jira) 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 that is either created locally or in Jira. 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). Upon selecting the "Jira" radio button, you can see the "Jira Usage Context" and "Project in Jira", Worksoft SaaS fetches all the open issues created in the specific Jira Project context and populates the "Link" dropdown. 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. 

   

View Reported Issue(s)

You can view the issues either created locally or in Jira that are linked to a Test Run 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. The Jira Usage Contexts dropdown will not be shown when you select this option.


  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 perform search for the issues reported in Jira by selecting the 'Issues in Jira' radio button.


  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. Jira Usage Context: If you have multiple Jira usage contexts, you can select one or more of them from the dropdown.
  4. Date of the test execution:  You can select the execution date range and when the tests are executed in Worksoft SaaS   
  5. Date of the issue reporting into Jira: You can select the date range when the issues are logged into Jira if needed.

For the filtered issues which are filtered in the grid, you can see the Jira Usage Context and the Issue Key information in the popover by clicking on the blue ribbon which is shown in the 'Summary' field. On clicking on the 'Copy to Clipboard' icon displayed next to the Issue Key would copy the Jira Issue URL which on pasting in another tab would redirect to the respective Issue in Jira application.

When you select the checkbox 'Show issues archived within Worksoft SaaS', the issues that are delinked from this test run can also be viewed.


Feedback and Knowledge Base

(thinking…)