- ID
- 3f75a7a8-ddbe-4834-ab38-e35911d1b231
MMPY-174 Add created by to a hold
- source :: https://multimediallc.atlassian.net/browse/MMPY-174
- epic :: MMPY-198 Compliance Holds, Fraud Holds, and Banned Payees
- tags :: Falcon Nest Project Story Falcon Nest Project
- status :: Status - Complete
DONE Fix PR issues
- ID
- 5850e72e-3e12-6c45-2693-25a1859461f8
Background
Holds were implemented, without sufficient analysis of the workflows surrounding
them. They function as needed: they can be created, they stop transfers from
sending if they exist for a user, their “removed” data acts as both a closure
and a record of when it was closed.
There is some confusion as to how a note is supposed to behave, what it means,
and there are some transparency issues.
Holds will be able to be created 1) by a logged in user in django admin, 2) by
the system as a course of other events, 3) via API by a user in a remote system
Potentially an “origin” or similar field for API, Django Admin, and System could
be useful here
Requirements
DONE Add created by field to holds
- ID
- b0e24111-fb22-eacd-d9b6-d6086ae2ff80
DONE Use a foreign key field to manage created by user
- ID
- 3d9e7633-b849-3655-dbe3-8883035018b7
GIVEN
A user with access to django admin
WHEN
The user creates a hold
THEN
The user is added to a created by field, and this is visible in django admin
Secondary Requirements
DONE Add default created_by user for automated holds
- ID
- 7d753b65-292b-4176-69a9-8865093a8a55
--
GIVEN
A user has no valid account or no tax information
WHEN
A hold is being created
THEN
The user by should be “system user”, and this is visible in django admin