Org Web Adapter

Editing pages/mmpy_173_add_description_to_a_hold.org

:PROPERTIES:
:ID:       efa47941-44f7-4791-8dfe-546bb3ac8ba7
:END:
#+title: MMPY-173 Add description to a hold

- source :: https://multimediallc.atlassian.net/browse/MMPY-173
- tags ::  [[id:4b532967-a1d9-45f4-b1f0-9a02ad540ff0][Falcon Nest Project Story]] [[id:7c3bbb4e-d079-42c4-992c-3e76210911f4][Falcon Nest Project]]
- epic :: [[id:88adb9ec-ab52-4d87-8625-6cf72d01612c][MMPY-198 Compliance Holds, Fraud Holds, and Banned Payees]]

* 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.

Hold types are helpful, if a user has a hold of type “no active account” we can
then take action when they have an active account.

In order to support a user being able to tell two “compliance” or “fraud” holds
apart, we need to be able to see a description that is more granular than
“compliance”. We also want a system that is resilient, and doesn’t require code
in our system to change if a new compliance type arises. The current system has
commented out compliance types, and a “free form” option.

* DONE Fix tests for query count :djadmin:feature:holds:mmpy173:project:work:multimediallc:
:PROPERTIES:
:ID:       1564db79-9be1-d103-a281-66a3d78b4517
:END:
* Requirements
** DONE Add description field to Holds in Django admin :djadmin:feature:holds:mmpy173:project:work:multimediallc:
:PROPERTIES:
:ID:       95f52377-6656-43aa-6fbb-9d89665f3a72
:END:

** GIVEN

A user with access to django admin

** WHEN

The user creates a hold

** THEN

The user has a description field available to them

* Secondary requirements
** DONE Add default description for no valid account holds :holds:feature:mmpy173:project:work:multimediallc:
:PROPERTIES:
:ID:       df2ce86d-b942-9324-38c6-020e98fbe76a
:END:
** GIVEN

A user has no valid account

** WHEN

A hold is being created

** THEN

The description field should be “No active payout account”

* Tertiary requirements
** GIVEN

A user has no tax information on file

** WHEN

A hold is being created

** THEN

The description field should be “No tax information”