split clone issues.md

Split / Clone Issues

Overview

When a large issue contains many parts, not all inventory needs to be treated the same way. Splitting inventory into detailed issue tickets allows teams to apply the right disposition to the right parts—for example, scrapping defective pieces while reworking others that can be repaired and returned to production. This flexibility ensures that inventory is not lumped into a one-size-fits-all decision, reducing unnecessary waste and enabling faster resolution.

The split workflow maintains full traceability by linking detailed tickets back to the original issue. Key fields, such as cause or condition, can be copied to ensure consistency, while each new ticket holds its own inventory assignments, quantities, and notes. This structured approach gives teams a clear, tabular view of related issues, helping them quickly navigate across hundreds of parts and resolve them with the appropriate teams. The result is better control, faster decision-making, and improved overall quality management.

Procedure for Splitting Inventory Issues into Detailed Tickets

Key Steps

1. Understanding the Need for Splitting Issues 0:00

2. Accessing the Issue Menu 0:39

3. Creating Detailed Tickets 1:03

4. Adding Notes and Disposition Type 1:36

5. Selecting Inventory for the New Ticket 2:00

6. Adjusting Inventory Quantities 2:40

7. Removing and Assigning Inventory 3:05

8. Creating Additional Tickets as Needed 3:37

9. Verifying Inventory Changes 4:41

10. Reviewing Related Issues 5:12

11. Copying Settings and Attributes 5:34

12. Final Review and Navigation 6:03

Link to Loom

https://loom.com/share/1a2feadfc5b44d86ac516572242f042c