FAS - Enhancements to Search functionality
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
* As a FAS user
* I want the entity number and reference number search functions to be more relaxed in their matching criteria
* so that small differences in formatting can be accounted for
* As a FAS user
* I want the Receipt Number field to be renamed to Cash Receipt Number (or something similar)
* so that it is clear that this value is for the receipt for Cash payments
**Acceptance Criteria**
**Scenario 1: Relaxing search functions**
* GIVEN ... a routing slip has an entity number such as "BC 12345"
* WHEN ... the user searches for entity number "BC12345"
* THEN ... the given routing slip should be in the search results
...
**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**
* Do you know a possible contact person to reach out (from the other team)?
**Validation Rules? (If yes, list here)**
**Design**
@xxx - please link the Design here
----
**Link to DoR for a US/ Feature**
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Relationships.md
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoR%20-%20Entity.md
**Link to the DoD for a US/ Feature**
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Relationships.md
https://github.com/bcgov/entity/blob/master/.github/ISSUE_TEMPLATE/DoD%20-%20Entity.md
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the FAS routing-slip search entry points and the UI containing the Receipt Number label; verify how entity and reference numbers are matched. Done means formatting differences such as “BC 12345” and “BC12345” return the same result, and the cash receipt label is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100