Roles: L4-Engineer

"Area Path" and "Iteration Path" are standard fields in Azure DevOps (ADO), and they are used to organize work items by product classification, team, and time period.

This guide describes how bugs – when they are created in Azure DevOps (ADO) – also are classified to ensure that they are handled with regards to their severity and potential impact.

The definition of done (DoD) for L4 bugs are the checks performed when an L4 bug is considered completed.

During L4 fault tracing it may be required to send a debug release outside of PCP. This has to be handled with care as it isn't a formally released software.

A product issue is a uniquely identified problem impacting a product, requiring clear communication with various stakeholders. It must be documented with accurate information and version details and managed in parallel with bug management and product releases.

This guide describes how to determine if a malware suspicion is correct or false and how to handle both scenarios. It also includes information about how malware is detected in ABB software.

A bug is an unexpected problem in the software or hardware which can be reported for any issue in a product by e.g. product managers, product owners, test engineers, or customers (via L3 or L4 Support).

The process is mainly divided into two parts: continuous maintenance of existing products during the product life cycle, and an eventdriven part handling both customer problems via Support Level 3 and manufacturing problems. The process covers both hardware and software.

The L4 engineer evaluates issues together with L3 Support and identifies either a workaround for the customer problems or creates product defects to be added to stream and team backlogs for corrections in future releases.

This guide explains what a product issue number (PIN) is and how it is used within the PCP organization.