Search Request history by applicant name

* As an analyst
* I want to search request history by applicant name
* so that I can view previous requests by the same person

**Assumptions & Scope**
What are the assumptions for this story?
Only see requests made in request queue within new system for now

What is in and not in scope?
Integration with AXIS to see historical requests

**Acceptance Criteria**

**Scenario 1: Filter by applicant name - happy path**
* GIVEN an analyst is on the request queue
* https://jacklyn808742.invisionapp.com/console/share/XU2L77IGEA/631997879
* And the intake analyst enters a known applicant name (last name, first name, last name and first name) in the search field
* WHEN the intake analyst clicks 'Apply'
* THEN only the requests made by applicants with those names will appear,
* AND the requests will be sorted alphabetically by applicant name with Unopen at top (by date submitted from newest to oldest), in the middle by Open (days left, less to more), and at the bottom Closed (by date closed, newest to oldest).

**Scenario 1: Filter by applicant name - sad path**
* GIVEN an analyst is on the request queue
* https://jacklyn808742.invisionapp.com/console/share/XU2L77IGEA/631997879
* And the intake analyst enters an unknown applicant name in the search field
* WHEN the intake analyst clicks 'Apply'
* THEN the analyst will see a message that the applicant was not found

**Scenario 3: Search as a watcher on a request**
...

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

Start by locating the request queue and its existing search or filter behavior; the issue provides no file or test names. Confirm the missing scenarios and design dependency before implementing, then verify that known names filter and sort requests correctly and unknown names show the specified message.

Written by the indexing model from the issue text.