# Contain Affected Inventory

### Overview

When a defect or anomaly is discovered, the first priority is containment—making sure potentially affected parts do not continue down the production line or reach customers. Quickly attaching inventory to an issue ticket allows teams to isolate all related parts, whether they share a lot, serial number, or another attribute. This immediate action reduces risk, prevents costly escapes, and ensures every affected unit is accounted for.

By grouping inventory to a single issue ticket, manufacturers also gain a clear foundation for root cause analysis, disposition, and compliance. Instead of manually tracking affected parts across multiple systems, teams have one structured place to document the issue, evaluate corrective actions, and ensure regulatory traceability. The result is faster response, fewer errors, and stronger overall quality control.

Associating inventory with an issue can also affect its status. Depending on the issue's disposition type and its **Availability Behavior**, inventory may stay available, become **Unavailable** until the issue is resolved, or become permanently unavailable. Inventory already in **Installed**, **Work In Progress (WIP)**, or **Scrapped** status is not changed by this rule. For configuration details, see [Disposition Types](/quality/disposition-types.md).

### How To

#### Key Steps

**1. Access the Inventory Screen** [0:00](https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547?t=0)

![](https://loom.com/i/056720c4e99f49b88048fd2cdd1f4abd?workflows_screenshot=true)

* Open the ION application.
* Navigate to the inventory screen via the side bar to begin the process of filtering and selecting parts.

**2. Filter Inventory by Shared Attributes** [0:55](https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547?t=55)

* Determine the shared attribute for the inventory you want to group (e.g., lot number, serial number).
* Use the filtering options to display only the relevant inventory items.

**3. Select Relevant Inventory Items** [1:08](https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547?t=68)

![](https://loom.com/i/9b51e0656d0e4b6f93a63a097fcbd05f?workflows_screenshot=true)

* Review the filtered inventory list.
* Select all items that share the common attribute (e.g., all items from lot two).

**4. Open the Command Menu** [2:11](https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547?t=131)

* Press Command + K (Mac), Ctrl + K (Windows) to open ION's command menu.

**5. Create an Issue Ticket** [2:22](https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547?t=142)

![](https://loom.com/i/5b0757ae97b84856b572b4534fc34a62?workflows_screenshot=true)

* In the command menu, select the option to create an issue.
* Enter a title for the issue (this is the only required field).
  * Example title: "Identified parts outside of run execution step."
* Click to create the issue.

**6. Review the Created Issue** [2:59](https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547?t=179)

![](https://loom.com/i/e2c8223615bc432583e5b805a12ba257?workflows_screenshot=true)

* After creating the issue, navigate to view it.
* Confirm that all selected parts are associated with the issue ticket.

#### Cautionary Notes

* Ensure that the filtering criteria accurately reflects the inventory you wish to group to avoid misclassification.
* Double-check the title of the issue for clarity and relevance to the identified parts.

#### Tips for Efficiency

* Familiarize yourself with the filtering options to quickly access relevant inventory.
* Use keyboard shortcuts (like Command + K) to streamline the process of creating issue tickets.

#### Link to Loom

<https://loom.com/share/0ec507b8846e4d7fb212fb0713fb6547>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual-v2.firstresonance.io/quality/contain-affected-inventory.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.