Filter Request Queue by file number

* As a (type of user)
* I want (goal)
* so that (reason/ why/ value)

**Assumptions & Scope**
What are the assumptions for this story? At this point of maturity, the search function does not need to advanced. We will likely need to upgrade search functionality down the line, once the database grows; no backend search needed (just local)

Does the selection of request type (e.g. just general) impact the filter? Probably not.

The filter will only show requests made in the new application at this time.

**Acceptance Criteria**

**Scenario 1: Filter by file number - happy path**
* GIVEN an analyst is on the request queue
* https://jacklyn808742.invisionapp.com/console/share/XU2L77IGEA/631957825
* AND the intake analyst enters a valid file number in the search field
* WHEN the intake analyst clicks 'Apply'
* THEN only the request with that file number will appear, including an 'Open' or 'Closed' request

**Scenario 2: Filter by file number - sad path**
* GIVEN an analyst is on the request queue
* https://jacklyn808742.invisionapp.com/console/share/XU2L77IGEA/631957825
* AND the intake analyst enters an invalid file number in the search field
* WHEN the intake analyst clicks 'Apply'
* THEN the analyst will see a message that the File Number is invalid
...

**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 at the request queue and trace the local search field and Apply action described in the issue. Confirm the design and validation rules before implementation; done means valid file numbers show matching open or closed requests, while invalid numbers produce an error message, with tests covering both scenarios.

Written by the indexing model from the issue text.