LogoLogo
👉 Get a free ITSM ebook
Appsvio Test Management
Appsvio Test Management
  • Get Started
  • About ATM
    • Organizing Tests
  • Architecture
    • Objects & Relations
    • Custom Fields
  • Pricing Model
  • SETTING-UP PROCESS
    • Testing Hub
    • Testing Setup
    • Permissions
    • Environments
  • Testing in ATM
    • Requirements
    • Test Cases
      • Test Steps
        • Versioning
    • Test Plans
    • Test Executions
      • Test Case Executions
    • Defects
  • Reporting
    • Traceability
    • Test Coverage
  • Search in JQL
  • Integrations
    • Jira Automations
  • Resources
    • Roadmap
    • Release Notes
  • Contact our Support
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com © 2025 All rights reserved

On this page
  • Test execution
  • Test Case Execution

Was this helpful?

Export as PDF
  1. Testing in ATM

Defects

Defects portray the differences between the end-product and current versions. How do they work in ATM?

PreviousTest Case ExecutionsNextTraceability

Last updated 3 days ago

Was this helpful?

Defects highlight the differences between the objectives, goals of software functionalities and the reality. They are a straightforward information about what needs to be fixed and what issues need to be addressed. It goes without saying that identifying defects is a crucial part of testing and software development, as it guarantees a delivery of reliable and functional product.

Overall, Defects in ATM can be created from 3 places - Test Execution (TE), Test Case Execution (TCE) and a step in the TCE. Below, we are describing each of the paths for creating defects.

Defects and Templates go together! Creating templates for a bugs can help testers maintain consistency across items and save their time. Check out our Issue Templates Agent on and for more details!

Test execution

Within each Test Execution work item view, the users can find a Defects tab. There, existing Defects can be linked to the execution or the users can add Defects. All of this is done with respective buttons at the top of the tab. The Link defects button opens up a search dialog window, where users can select defects either as a basic search or an advanced JQL one.

The Defects tab gathers the linked defects in a list as well. The table contains following details:

  • Defect key

  • Summary

  • Priority

  • Status

  • Date of creation

  • Date of latest update

  • Fix versions

  • Assignee

Test Case Execution

The Test Case Execution dialog window also contains a Defects tab, which collects information regarding this testing element. Following data is collected in a table:

  • Defect key

  • Summary

  • Relation

    • This column shows whether the defect relates in general to the selected TCE or has roots in a specific step of TCE

  • Priority

  • Status

  • Creation date

  • Assignee

Within this tab, the users can also add new or link already existing Defects.

Add defect button will open the Create work item dialog window. If the user has set a default project and work type while configuring the Testing Setup, the project and the work type will be automatically filled-in in the Create window.

TCE Step

Defects can also be added to an individual Test Step in the Test Case Execution dialog window. The button that allows to perform this action can be found at the bottom of each step. While creating a defect from the TCE Step, the description field will be automatically filled-in.

The opening of the Create work item view, to add Defects from the level of Test Steps, automatically transfers the information in the Test Steps into Defects description.

Marketplace
app documentation