-
Notifications
You must be signed in to change notification settings - Fork 3k
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-07-10] [HOLD for payment 2024-07-02] [Details Revamp] Update Policy Expense Report/Requests Name Display Logic #42076
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
Triggered auto assignment to @trjExpensify ( |
|
Triggered auto assignment to Design team member for new feature review - @dannymcclain ( |
Still held. |
Hi, I'm Tymoteusz Kałuzieński from Software Mansion, the expert agency, and I'm working on this issue. The PromotedActionsBar has been merged so as far as I know this should be unheld. |
Excellent! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.1-19 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-07-02. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@trjExpensify @grgia I require payment as C+ reviewer of PR: #43251 (comment). Notes: |
@grgia, can you confirm on the regressions so we can move to paying Kevin what's due here? |
This PR covered multiple app flows and required extensive testing & back-n-forth with the PR author, design team and engineers (see #43251). Given this I propose a $500 bounty for reviewing this, minus regression penalty if we think that better testing on my part could've prevented all regressions. 🎉 Good work everyone, I think this PR was successful in terms of achieving the requirements while having a farely low regression count given the changes! |
Payment Summary
BugZero Checklist (@trjExpensify)
|
Bumped on Slack @ https://expensify.slack.com/archives/C01GTK53T8Q/p1720029343489579 I think it's safe to assume there was at least 1 regression here, not sure if more than 1 regressions would factor into the final payment amount. If that's true then we should wait for input, otherwise I think we can move forward with this given that we can't seem to be able to reach grgia on any channel. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.3-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-07-10. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Yeah, each regression counts (guide). That said, I'm happy to move on at $250 with this. Payment summary above has been updated, and I've sent an offer. |
@trjExpensify That's fine with me! Offer accepted, thank you! |
Paid, closing! |
https://docs.google.com/document/d/1-xSZdSZZIuIl0fPO7yypkKfcbWEsnNFAs50ptgL3Gnw/edit#bookmark=id.47hdcwyvv08k
Held on #42071
Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: