[cnathe]

Rationale

This PR makes assay run QC history show QC state changes made from a folder other than the run's own, and makes the QC state update page work for runs in another folder. QC audit events were stamped with the request's container, so changes made from the project-level app never appeared in the run's history. Separately, the server-rendered QC state page looked runs up in the current folder only. Issue: GH Issue 1619

Related Pull Requests

• GH Issue 1619: Fix cross-container handling in assay run QC history and QC state update page #8217
• https://github.com/LabKey/premiumModules/pull/814
• https://github.com/LabKey/limsModules/pull/2560

Changes

• QC state audit events are stamped with the run's container going forward.
• Both QC history views (the app's run details page and the LKS QC State page) include events stamped in the run's folder or any parent folder or child folders the user can read, so existing mis-stamped events now show without modifying audit rows.
• The QC history container scope is fixed server-side, so a container filter URL parameter can no longer widen the elevated audit query, and the run permission check uses assay read permission.
• The QC state update page uses the runs the action already validated, so it shows the current state, QC state options, and comment requirement for runs in other folders.

[labkey-klum]

This is a nice solution.