Justin/APPEALS-46818

[sulak-j]

Resolves Update Correspondence Assignment/Reassignment Banner Verbiage

Description

Please explain the changes you made here.

Acceptance Criteria

• Code compiles correctly

Testing Plan

1. Go to Jira Issue/Test Plan Link or list them below
2. Log in as an inbound ops team admin user (supervisor)
3. Go to the unassigned tab, find an NOD correspondence, and select this checkbox
4. Find a user with no permissions from the inbound ops team dropdown and assign the correspondence to this user
5. The banner header on the next page should say Correspondence was not assigned to {user}, and the banner message should say Case was not assigned to user because of NOD permissions settings.
6. Go to the unassigned tab, find a non-nod correspondence, and select this checkbox
7. Select a user that has a full queue from the inbound ops team dropdown and assign the correspondence to this user. (I set this up in local by manually assigning 60 correspondences to one user first, but there may be users set up in UAT that are close to max capacity to test this)
8. The banner header on the next page should say Correspondence was not assigned to {user}, and the banner message should say Case was not assigned to user because maximum capacity has been reached for user's queue.
9. Go to the assigned tab, find an NOD correspondence, and select that checkbox. Repeat step 4
10. The banner header on the next page should say Correspondence was not reassigned to {user}, and the banner message should say Case was not reassigned to user because of NOD permissions settings.
11. Go to the assigned tab, find a non-nod correspondence, and select this checkbox. Repeat step 7.
12. The banner header on the next page should say Correspondence was not reassigned to {user}, and the banner message should say Case was not reassigned to user because maximum capacity has been reached for user's queue.

Note: Thid ticket changed the banner title and message texts for:

• Assignment NOD failures
• Reassignment NOD failures
• Assignment max capacity failures
• Reassignment max capacity failures
• Assignment sensitivity level mismatch failures (I believe Jeremy has test steps for this in UAT)
• Reassignment sensitivity level mismatch failures (Again, should be testable in UAT)

Frontend

User Facing Changes

• Screenshots of UI changes added to PR & Original Issue

BEFORE|AFTER
Before:

After:

---|---
Before:

After: