Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MHR - Remove alert bar in the QS account when a unit note is cancelled #18292

Closed
1 task done
chdivyareddy opened this issue Oct 23, 2023 · 2 comments
Closed
1 task done
Assignees
Labels
Assets bug Something isn't working

Comments

@chdivyareddy
Copy link
Collaborator

chdivyareddy commented Oct 23, 2023

  • If the unit note being cancelled had an alert bar on the MHR page, then remove alert bar and any restrictions in the QS account.

Steps to reproduce:

  • Select an MH Registration that has unit notes REST, NCON, CAU, CAUC, CAUE (Eg: 107829)
  • Add the MHR to the QS account which displays alert bar and restricts user from making changes to the registration as expected
  • Now, cancel the unit notes from the staff account and navigate to the QS account.
  • LOCKED badge gets removed but the alert bar is still displayed and restricts user from filing a transfer

image

image

Staff View:
image

Design Link:

image

https://www.figma.com/file/FVvx7KgHDCAfejklfoue3L/MHR---Unit-Notes?type=design&node-id=1792-43093&mode=design&t=g1coU4P3mbpPxbcC-0

@cameron-eyds
Copy link
Collaborator

cameron-eyds commented Jun 18, 2024

Tested this with the adding of a Confidential Note (it blocks QS) on the Staff Side, verified blocked on QS side.
Once cancelled, and reloaded the QS Dashboard, the QS was free to make changes as expected.

@chdivyareddy
Copy link
Collaborator Author

Verified in DEV using MHR 108305.

image.png

image.png

image.png

image.png

image.png

@PCC199 PCC199 closed this as completed Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Assets bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants