Skip to main content

Create or Link a Defect During a Test Run

Record a testing issue, create a Jira defect manually or with Vansah Intelligence, or link an existing defect to the relevant Test Run step.

When a test reveals a problem, create a Jira defect from the relevant Test Run step or link an existing work item. The link keeps the defect connected to the test execution where you found the issue.

Before you begin

  • Open the correct Test Run and iteration so the defect is linked to the intended execution.

  • Make sure you have access to the destination Jira space and permission to create work items there. Linking a defect to the execution also requires permission to execute Test Cases in Vansah.

  • For AI-assisted drafting, Vansah Intelligence must be enabled and available to your account.

Record what happened

  1. Open the Test Run and expand the relevant Test Case or step.

  2. Enter the Actual Result: describe what you observed and how it differs from the expected result. Save your changes.

  3. Set the step’s result to the appropriate status, such as Failed. Add useful screenshots or other evidence.

For example: “Selecting Place order displays a server error. The order is not created.” Include enough information for another person to reproduce the issue.

Create a defect manually

  1. Open the defect menu beside the relevant step.

  2. Select Add new defect. Jira’s work item creation form opens with details prepared from the test execution.

  3. Check the destination Jira space and choose Bug, or the defect work item type used by your team.

  4. Review the summary and description. Check the steps to reproduce, expected result, actual result, and Test Run link. Complete any fields required by your Jira configuration.

  5. Select Create in Jira.

  6. Return to the Test Run and confirm that the new work item key appears among the step’s linked work items.

The manual draft can include the steps up to the selected step, its expected result, the recorded actual result, and a link back to the Test Run. Review the draft before creating the work item.

Link an existing defect

  1. Open the same defect menu and select Link/Manage existing defects.

  2. Use the Jira space picker if the defect belongs to another space. Search for its work item key or summary.

  3. Select the matching work item. The link is saved when you select it.

  4. Check that the defect appears in the linked work item list, then close the panel.

Use this option when a defect already exists so you can associate the execution with it without creating a duplicate.

Draft a defect with Vansah Intelligence

When Create a defect with AI is available in the step’s defect menu, Vansah can prepare defect details from the test and execution context.

  1. Record and save the actual result for the relevant step.

  2. Open the defect menu and select Create a defect with AI.

  3. Wait for Jira’s creation form to open with the generated details.

  4. Review and correct the summary, description, reproduction steps, and expected and actual results. Select the destination Jira space and defect type, and complete its required fields.

  5. Select Create, then confirm that the new defect is linked to the execution.

AI-generated text can be incomplete or incorrect. Review it before creating the Jira work item. See How Vansah Intelligence Works for more about the context used.

Video: Generate Defects with AI for Jira. Menu wording and layout may differ from the video; follow the current labels in the steps above.

If creation or linking does not finish

  • If the work item is created but linking fails, find the new Jira work item and use Link/Manage existing defects to link it. Check Jira before creating another defect.

  • If Vansah reports that screenshots could not all be attached, open the created defect and check its evidence. Add any missing attachments in Jira.

  • You cannot link the same work item as a defect when the Test Run was created against that work item. Use the separate defect work item instead.

  • If an option is unavailable, ask your administrator to check your Jira access, Vansah execution permission, and Vansah Intelligence access where applicable.

Did this answer your question?