Closed justin-lepitzki closed 8 months ago
Hey team! Please add your planning poker estimate with Zenhub @AlexZorkin @hamed-valiollahi @jig-patel @kevin-hashimoto @prv-proton
As a BCEID user part of an organization that is unregistered, the 'New transfer' button on the transactions page is still visible to me. If an organization is flagged a 'unregistered', the 'New transfer' button should not be visible to any of the users connected to that organization and the users should not be able to start filling out the required fields of a new transfer, should not be able to save it, and should not be able to sign and send a new transfer.
Currently, as a BCeID user that is part of an unregistered organization, I can still see the "New transfer' button on the transaction page, fill out required fields for a new transfer, sign and send a transfer that will be visible and and able to be signed and submitted by the purchasing organization.
In addition: If an organization becomes unregistered after a new transaction has already been saved or signed and sent, there should be one final validation in place for a IDIR user with a director role before the transfer is recorded. For these transfers that were sent when an organization's status was "registered" but changes to "unregistered" before being recorded, the director should receive an error validation stating "organization unregistered" if one or both of the organizations are unregistered.
This validation check for a registered organization should also be added to either card #325 and/or #326
Description: To develop the transfer registration flag feature that controls whether an organization can buy and sell credits. A registered organization (yes flag) can buy and sell credits whereas a unregistered organization (no flag) cannot buy/sell credits.
Wireframes:
Purpose and benefit to user:
Acceptance Criteria:
Development Checklist: