-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-09-03][$250] [Search v2.1] [App] Create Amount filter #46036
Comments
Triggered auto assignment to @trjExpensify ( |
Hi! I'd like to work on this issue :) |
SOLD! |
Job added to Upwork: https://www.upwork.com/jobs/~01a66609e4336f130d |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ZhenjaHorbach ( |
@luacmartins What should a page with this filter look like? Amount filter is a range, so we can handle it by having two inputs (from and to) on the page, do you think it will be ok or should we handle it in a different way? |
@Expensify/design do we have any mocks for the amount filter page? |
@trjExpensify, @luacmartins, @WojtekBoman, @ZhenjaHorbach Eep! 4 days overdue now. Issues have feelings too... |
Gonna reassign C+ as per this comment |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@trjExpensify, @luacmartins, @WojtekBoman, @rayane-djouah 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
@WojtekBoman, are you working on this? |
I'll take this from Wojtek after I fix PR comments on #46736, as Wojtek just started a new Expensify project. |
PR is on staging. |
Note The production deploy automation failed: This should be on [HOLD for Payment 2024-09-03] according to #47873 prod deploy checklist, confirmed in #47343 (comment). |
Chill Melv, payment isn't due. |
Payment is due |
Payment summary as follows:
Paid, closing. |
Implement this section of the design doc for the Amount filters only!
cc @adamgrzybowski @Kicu @WojtekBoman @Guccio163
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: