Enhance Filtering Options on Earnings Page (Add “Remove Filter” & “All” in User ID Dropdown)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
- Domain
- frontend
Research direction
No files or tests are named. Start by locating the Earnings page and its User ID dropdown, then trace how the date and user filters are applied. Done means users can reset all filters and select “All” to view earnings without a user-specific filter.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Yes. The current Earnings page lacks essential filter controls that affect usability:
Once filters like date range or User ID are applied, there’s no clear way to remove or reset them without reloading the entire page.
The User ID dropdown only allows selecting individual users, with no “All” option to view earnings across all users at once.
These limitations make it harder to conduct quick analyses or generate comprehensive reports.
Describe the solution you'd like
Add a “Clear Filter” or “Reset” button to remove all applied filters and return to the default view.
Add an “All” option to the User ID dropdown, enabling a broader view of earnings without narrowing down to a single user.
Describe alternatives you've considered
Manually refreshing the browser (inefficient)
Selecting each user individually (not scalable for large user bases)
Additional context
These enhancements would improve the admin experience, making earnings management more intuitive and efficient, especially for tasks like support, auditing, and financial reporting.
- 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