I am developing NoticeTrace, a Jira Forge application for supplier-quality operations. When a supplier notice identifies affected component lots, the application traces those lots through as-built records to the builds they entered, and creates linked investigation tasks under human confirmation. It reports only Trace found / No trace found in these records / Unresolved — it never declares a build safe.
The workflow: a supplier notice arrives naming affected component lots. The app extracts supplier / part / lot identifiers from the notice text, each with a quoted source span, and a human confirms them. It then deterministically traces the recorded lot-to-build relationships in the as-built records (CSV upload) and reports per build. Linked Jira investigation tasks are created only after human confirmation, idempotently — re-running never duplicates a task.
Sample supplier notice (SYNTHETIC): 'Supplier notice SN-2026-114, Acme Capacitors: lots C-2214 and C-2215, part CAP-10uF-25V, shipped 2026-03-02 to 2026-03-19, may exhibit elevated leakage.'
Sample as-built rows (SYNTHETIC): B-1001 | CAP-10uF-25V | lot C-2214 | Acme Capacitors | 2026-03-10 | Plant 2, Line A. B-1002 | CAP-10uF-25V | lot C-2209 | Acme Capacitors | 2026-03-08 | Plant 2, Line A. B-1003 | RES-1k-0603 | lot R-8810 | Beta Resistors | 2026-03-11 | Plant 1, Line C. Expected trace for lots C-2214/C-2215: B-1001 = Trace found; B-1002/B-1003 = No trace found in these records.
The workflow is being validated with manufacturing and supplier-quality practitioners before development. Three points require practitioner confirmation:
1. Whether supplier notices are traced from lots to builds in this manner in practice, and in which system.
2. Whether the sample as-built records reflect real records — which fields are present, missing, or unrealistic (batch vs lot? date codes? revision? serial-level trace?).
3. Whether Jira is used for the resulting investigation tasks in your organisation.
A reply in this thread is sufficient. Respondents' names, roles, and assessments will be recorded as validation evidence for the project, with their permission. Validators who use Jira in their day-to-day work are particularly relevant — please state this in your reply.
Regards, Anmol Singh