Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.58k stars 2.92k forks source link

[HOLD for payment 2023-10-16] [$500] Approved requests shouldn't have a `delete` option #26419

Closed JmillsExpensify closed 1 year ago

JmillsExpensify commented 1 year ago

While we've already implemented logic preventing paid requests from being deleted, the same isn't true for approved requests, which we've just added. Accordingly, let's remove the Delete request option from the three dot overflow menu anytime a request has been approved.

Here's mock for clarity. Notice how I've removed the Delete request option. image

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01bd5a594a7f989566
  • Upwork Job ID: 1697326804261687296
  • Last Price Increase: 2023-08-31
  • Automatic offers:
    • cubuspl42 | Reviewer | 26523887
    • Pujan92 | Contributor | 26523889
melvin-bot[bot] commented 1 year ago

Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:

On to the next one 🚀

cubuspl42 commented 1 year ago

One of the reasons it took so long is that the issue was related to Teachers Unite / corporate policies, which require extra setup to test.

melvin-bot[bot] commented 1 year ago

Reviewing label has been removed, please complete the "BugZero Checklist".

melvin-bot[bot] commented 1 year ago

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.3.79-5 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

If no regressions arise, payment will be issued on 2023-10-16. :confetti_ball:

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:

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

JmillsExpensify commented 1 year ago

@cubuspl42 I think we should add a regression test so that this doesn't happen again. Do you agree and mind suggesting one?

JmillsExpensify commented 1 year ago

Based on the time between assignment and merge, here's the payment summary:

cc @Julesssss

cubuspl42 commented 1 year ago

@JmillsExpensify

@cubuspl42 I think we should add a regression test so that this doesn't happen again. Do you agree and mind suggesting one?

I don't have a strong opinion about adding the regression test. Here are the testing steps, if we decide to add one:

JmillsExpensify commented 1 year ago

I don't think this is specific to the TU policy, but instead to all approved requests. That said, I can make those tweaks in the regression test. Now that @Pujan92 has been paid out, I'm going to close this issue.