Below is the list of Panaya standard test fields, their location in the Panaya application, and their intended purpose and description.
Field Name | Location | Field Description and Purpose |
Reopen count | Defect List | Tracks the number of times a defect has been reopened after being previously closed, providing insight into the history of reoccurring issues and their resolution status. |
Reopened on | Defect List | Indicates the date when a closed defect was reopened, allowing for tracking the timeline of when and why issues resurface in the software development lifecycle. |
Found in test name | Found in export | Specifies the name of the specific test or testing phase in which a defect was discovered, helping to associate the defect with a particular testing context. |
Found in step description | Found in export | Identifies the specific test step or action where a defect was discovered, helping to pinpoint the exact location within a test scenario where the issue occurs. |
Test ID / Applicative test ID | Found in export | Associates a defect with a particular test case or scenario, linking the defect to its corresponding test for comprehensive tracking and resolution. |
Transaction | General | Refers to the specific business operation or process within SAP that is associated with a defect. It aids in identifying the exact transaction where the reported issue occurs for precise analysis and resolution. |
Transport request | General | This refers to the specific request or container used in SAP to bundle and deploy changes, enhancements, or fixes related to a defect across different system environments. It aids in tracking and managing the movement of changes within the software development lifecycle. |
Status | Defect Level | Indicates the current state or stage of resolution for a defect identified during testing or other stages of the software development lifecycle. |
Detected by | General | Captures the person or entity initially identified a defect during testing, facilitating communication, accountability, prioritization, analysis, and compliance in the software development process. |
Detected on | General | Records the date when a defect was first identified during testing, aiding in tracking the timeline and history of defect discovery. |
Cycle | General | Identifies the specific testing cycle or phase during which a defect was found, aiding in contextualizing the defect within the testing process. |
Resolved on | General | Indicates the date when a defect was successfully addressed and resolved, helping to track the timeline of defect resolution within the testing and development process. |
Closed on | General | This date signifies the date when a defect was formally marked as closed after it has been thoroughly addressed, validated, and considered resolved in the software development lifecycle. |
Resolved reason | General | Specifies the rationale or explanation for why a defect was considered resolved, providing insight into the decision-making process during defect resolution. |
Due Date | General | Specifies the deadline by which a defect should be resolved, aiding in time management and prioritization of defect resolution efforts within the software development process. |
Contains personal information | General | It indicates whether a defect report contains sensitive personal information, helping to manage data privacy and compliance concerns within the defect tracking process. |
Link to screenshot | General | It provides a direct link to a screenshot or visual representation associated with a defect, enhancing the communication and understanding of the reported issue. |
Subject | General | It provides a concise and descriptive title for a defect, aiding in quickly identifying and understanding the nature of the reported issue. |
Tests | Test Level | Indicates the number of tests or test cases associated with a specific defect, providing insights into the extent of testing coverage for that particular issue. |
Attachments | Attachments | It allows users to add and associate additional files, documents, or resources with a defect report, providing supplemental information for thorough issue analysis and resolution. |
Found in release | General | Indicates the software release or version in which a defect was initially discovered, aiding in tracking and managing defects across different software iterations. |
Hashtags | General | It allows users to assign descriptive tags or keywords to defects, facilitating categorization, searchability, and organization of related issues. |
Last comment | Comments | Displays the most recent user-generated comment or note added to a defect, providing a snapshot of the latest discussions or updates related to the issue. |
Last commented by | Comments | Indicates the user or individual who most recently added a comment or note to a defect, helping to identify the source of the latest information or discussion about the issue. |
Last commented on | Comments | Displays the date and time of the most recent comment or note added to a defect, aiding in tracking the communication timeline and updates related to the issue. |
Last modified date | Defect Level | Indicates the most recent date and time when any modifications or changes were made to a defect, aiding in tracking the history and updates of the defect's information. |
Release | General | Indicates the specific software release or version to which a defect is assigned, aiding in organizing and managing defects within different stages of development. |
Requirements number | Requirements | Links a defect to a specific requirement or specification, enabling traceability and understanding of how defects relate to the project's functional or design specifications. |
ID | Defect Level | It assigns each defect a unique identifier, facilitating easy reference, tracking, and communication about specific issues within the defect management system. |
Description | General | It allows users to provide detailed information and context about a defect, aiding in a comprehensive understanding and resolution of the reported issue. |
Blocking next step | General | Indicates whether a defect is preventing the progression of the software development process, helping to prioritize and address critical issues that may hinder further development or testing activities. If answered 'Yes', the test cannot continue to be tested until the defect is resolved. |
Testing owner | General | Designates the individual or team responsible for overseeing and managing the testing efforts related to a specific defect, aiding in coordination and ownership of the defect resolution process. |
Planned development efforts (h) | General | It allows the project to estimate the amount of time or effort expected to be spent addressing a defect during the development phase, aiding in resource allocation and project planning. |
Actual development efforts (h) | General | This allows the project to record the real amount of time or effort spent addressing a defect during the development phase, aiding in evaluating resource allocation and project planning accuracy. |
Remaining development efforts (h) | General | Allows the project to estimate the additional time or effort required to complete the development work for a defect, aiding in monitoring progress and adjusting project timelines. |
Can be verified | General | Indicates whether a defect can be easily validated or tested by quality assurance teams, helping to determine the readiness of an issue for the verification phase. |
Need more information | General | Flags, whether additional details or clarification, are required to fully understand or address a defect, aiding in effective stakeholder communication for issue resolution. |
Age | General | Indicates the duration of time since a defect was initially reported, providing insights into the length of time an issue has been unresolved. |
Dev owner | General | Designates the individual or team responsible for overseeing and managing the development efforts related to a specific defect, aiding in coordination and ownership of the defect resolution process. |
Assigned To | General | Designates the person or team responsible for addressing a specific defect, aiding in the clear assignment of tasks and efficient defect resolution. |