MPDX-9121 Add Mutations to MHA

[kegrimes]

Description

Add graphQL delete, submit, and duplicate mutations to MHA. Also, updates UI based on new figma designs.

This PR also addresses these issues:

• When we save the form, we need to alert the user (ex. the Goal Calculator shows a snackbar every time it sends a mutation to the server to keep the user informed that the form is autosaving)
• Added loading states
• Disabled edit button if user is not allowed to edit
• Added "no edit access" component incase a user saves Edit page when they do not have permission
• Added "no request access" component incase a user saves New page when they are ineligible

Note: Dialog for past deadline date, pending status, and permission denied components are under review by Ryan and stakeholders. (Edit: They have been approved)

Testing

• Go to /reports/housingAllowance
• Create a new request, enter in values, and cancel request
• Create a new request and test submit functionality
• Check edit access after submitting request
• Check that each mutation works as intended
• Check updated current approved mha card design

Checklist:

• I have given my PR a title with the format "MPDX-(JIRA#) (summary sentence max 80 chars)"
• I have applied the appropriate labels (Add the label "Preview" to automatically create a preview environment)
• I have run the Claude Code /pr-review command locally and fixed any relevant suggestions
• I have requested a review from another person on the project
• I have tested my changes in preview or in staging

[github-actions]

Bundle sizes [mpdx-react]

Compared against c360f7f

Route	Size (gzipped)	Diff
/accountLists/[accountListId]/reports/housingAllowance	126.65 KB	+3.04 KB
/accountLists/[accountListId]/reports/housingAllowance/[requestId]	164.01 KB	+1.01 KB
/accountLists/[accountListId]/reports/salaryCalculator/edit	153.99 KB	-2.53 KB

[github-actions]

Preview branch generated at https://add-mutations-to-mha.d3dytjb8adxkk5.amplifyapp.com

[wjames111]

Looks great, thanks for doing all this work! Found a few minor things but nothing serious.

[dr-bizz]

Sorry, I've been super busy with SIT functionality. I passed this to Will to review. Will will be in on Dec 29th, and you can ask him to review, so I'm not blocking you.

[wjames111]

These updates look great! I'm struggling to get it working locally for me though, not sure if I'm missing something.

[kegrimes]

@wjames111 I am having trouble testing as well because I only have two requests that do not have the statuses I need in order to test. The first one is PENDING and the second is BOARD_APPROVED. I need a request to be IN_PROGRESS or ACTION_REQUIRED but I am not 100% sure how to do that. The update mutation only allows updates on the request attributes, so I can't update the status using graphQL.

The current data I am talking about comes from MinistryHousingAllowanceRequests query. Let me know your thoughts.

[wjames111]

Thanks for making these changes, it looks great! I did notice last I checked there was a failing test. Also this may be a side affect of not being able to update the status but I noticed the create MHA button bugs out a little after an existing MHA is cancelled.

Screen.Recording.2026-01-05.at.9.53.54.AM.mov

[wjames111]

@wjames111 I am having trouble testing as well because I only have two requests that do not have the statuses I need in order to test. The first one is PENDING and the second is BOARD_APPROVED. I need a request to be IN_PROGRESS or ACTION_REQUIRED but I am not 100% sure how to do that. The update mutation only allows updates on the request attributes, so I can't update the status using graphQL.

The current data I am talking about comes from MinistryHousingAllowanceRequests query. Let me know your thoughts.

@canac do you have any thoughts on this?

[canac]

@wjames111 @kegrimes I'd probably update the database directly or use stage-console if you need to make those changes. I can help you set that up if you need.

[kegrimes]

@dr-bizz Will has already reviewed some of this PR, but I added some mini updates to the MHA here. The process should now be very smooth in between each mutation. To test some changes, you may have to update status in the database. Let me know if you find something I missed!

Changing the View page and print functionality will be done in #1557.

[dr-bizz]

Really great work on this!! I can tell you've worked really hard on this 🔥 💯

I spotted some things that needed adjusting, but no major issues.

When you complete the MHA, or when you click on print on the dashboard, it should take you to the view page, and automatically bring up the print popup, so the user doesn't need to click on print.

Also, when you are editing an MHA, then gon back to the dashboard, it gets stuck showing the skeletons. I think this was the issue I mentioned in the comments below about using loading.

[kegrimes]

@dr-bizz The print window you mentioned is taken care of in this PR #1557.

Also, I could not recreate the issue where after you go back to the dashboard page, the page gets stuck showing the skeletons. Could the query have been taking a little bit to load? I've had that happen before.

[dr-bizz]

Amazing job!

[wjames111]

Looks great! Did a lot of work on this!