-
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 2023-11-30][$500][ECARD] CRITICAL: Settings - Add “Get physical card” button and necessary routes #22877
Comments
Job added to Upwork: https://www.upwork.com/jobs/~013b675735e78d2be9 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @sobitneupane ( |
Could you assign me to this @grgia ? 😄 |
Similar to the issue for adding the Expensify Card page. I think we can get started on this, but ultimately HOLD merging the PR on having the Expensify Card page itself ready. One way to rollout and get some early benefit from these changes would probably be something like:
|
@sobitneupane, @pac-guerreiro Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@sobitneupane, @pac-guerreiro 10 days overdue. I'm getting more depressed than Marvin. |
@sobitneupane, @pac-guerreiro 12 days overdue. Walking. Toward. The. Light... |
This issue has not been updated in over 14 days. @sobitneupane, @pac-guerreiro eroding to Weekly issue. |
@pac-guerreiro Is this issue on hold? |
Yes it is, but I'm working on it 😄 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.2-3 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 2023-11-30. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
I would like to clarify here that the two deploy blockers linked here are not truly regressions whose penalty should apply. The first blocker was not directly caused by the PR and we decided to dig into it in a follow up PR before merging this. More context here. The second blocker was a very minor design in-consistency which went through the design review as well. Given the above along with the size of the PR, I would like to request for penalty waiver if there is any. Let me know what you think @grgia! |
I also suggest no penalty. But you could review follow-up PRs caused by this PR, instead of letting other C+ review. Before, we had discussion that if C+ also tasks responsible for regression issues, no penalty applies sometimes. |
@situchan @allroundexperts I agree that the original C+ should handle follow-up issues from this PR. Sometimes, with the number of new issues created, especially deploy blockers that have an urgency applied, the auto assigner might be part of the confusion. @allroundexperts I agree that the padding issue is not a serious regression and that any blockers related to the follow-up should be handled in the follow-up we decided on before merging. For this specific issue, I think it's alright to waive the penalty- but for next time, I agree that any follow-ups should be reviewed by the original C+. Does that sound fair to everyone? |
Yep, sounds good to me! |
@allroundexperts, @grgia, @pac-guerreiro Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Ho @grgia! Thanks |
Triggered auto assignment to @abekkala ( |
Bug0 Triage Checklist (Main S/O)
|
Upwork job price has been updated to $500 |
Contributor+: @allroundexperts owed $500 via NewDot |
d;oh, sorry so messy here, should be all set/done @abekkala |
$500 payment approved for @allroundexperts based on comment above. |
HOLD ON #22873
Design Doc Section
https://docs.google.com/document/d/1rFxJ78vz5On6zSWzYa51B9v-tyLdC5pUsBeLOLig0t4/edit#bookmark=id.rl1asurfa7yq
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: