Waiting requests follow their depot's approver (mirrored from ACM-320)

Project: Engineering
Type: Story
Status: Done Done
Priority: Medium
Organization: Brakeline
Reporter: Ines Costa <ines.costa@acme-hq.example>
Assignee: Lukas Brandt <lukas.brandt@acme-hq.example>
Labels: brakelineapprovalsmirror
Components: identity-serviceportalnotifier
Created: 13 Oct 2026, 09:20 UTC
Updated: 22 Oct 2026, 14:00 UTC
Resolved: 22 Oct 2026, 14:00 UTC

Description

Mirrored from Emargen so account managers can follow it in Jira and link customer tickets to it. The work is planned and tracked in Emargen as slices and tasks; don't track work here.

What ships

When the person who approves a depot's requests changes, the requests waiting on them go to whoever approves at that depot now.
When nobody at the depot can approve, they go to the client's administrators, with a "No approver at this depot" line.
Each moved request keeps who it waited on before, and when it moved.
The new approver gets one email listing the requests that moved to them.

Started from Brakeline's six Leeds requests in September (SUP-1184).

Linked issues

relates to SUP-1184 Leeds requests missing Done
relates to SUP-1257 Halden Foods: penetration test summary when the report arrives Done
relates to ENG-1826 Brakeline: who a moved request waited on before, in the audit log export Backlog

Comments (1)

Ines Costa · 22 Oct 2026, 14:00 UTC

Shipped today. Pia is telling Brakeline on SUP-1184's thread.