Search Box on Dispatch Page Not Filtering Orders by Store Name
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by locating the admin panel's Dispatch page and its search handler, then trace how orders and store names are filtered. Reproduce the issue with an active store order and verify that searching by store name returns only matching orders.
Written by the indexing model from the issue text.
Description
Describe the bug
On the dispatch page in the admin panel, the search keyword textbox is not filtering orders based on the store name. Entering a store name into the search field yields no results, even when there are clearly visible orders from that store in the list.
To Reproduce
Steps to reproduce the behavior:
Log in to the admin panel
Navigate to the Dispatch page
In the search textbox, type the name of a store that has active orders listed
Observe that the search does not filter or return any matching results
Expected behavior
Typing a valid store name should filter and display only the orders associated with that store in real-time or upon submission.
Screenshots
Recording.2025-06-17.102544.mp4
Desktop (please complete the following information):
OS: Windows 11
Browser: Chrome
Version: [e.g., 123.0.6312.86]
Additional context
This bug affects the efficiency of order management by preventing admins or dispatchers from quickly narrowing down orders by store. It may be due to missing query logic or improper field mapping in the search functionality.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from patriciaperez90/react-native-based-uber-eats-clone-app
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2622 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
patriciaperez90/react-native-based-uber-eats-clone-app#2620 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2558 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2557 ·
All issues in patriciaperez90/react-native-based-uber-eats-clone-app
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100