Impossible to handle blocked targets when flagging took place in another part of the organization #2399
Labels
🐜 bug
Something isn't working
🐳 Large
A real chonky boy with lots of complexity.
🛑 potentially blocked
Potentially blocked by prerequisites (double check or ask someone, as it may have changed)
Description
A caller can flag a target using a feature called "Organizer Action Needed" (OAN). When that happens, the target is blocked from calling. This block is enacted in the entire organization tree, not just the specific organization where the call took place. But the UI to handle blocked callers does not understand this, so there is no way of handling a flag that took place in another organization.
This is probably limited by lack of functionality on the backend.
Steps to reproduce
Expected Behaviour
The list should contain anyone who's blocked, and the "Flagged calls" column should contain a exclamation point for anyone who's still blocked.
Actual Behaviour
The list contains all who are blocked, but the "Flagged calls" column is empty for people who are blocked due to flagged calls in the sub-organization.
Screenshots (if you have any)
Flagging in sub-organization (step 1)
Impossible to handle
The text was updated successfully, but these errors were encountered: