You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IOU - Comment in IOU report preview does not update after deleting money request #24365
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Sorry but no. All engineers are super busy with wave issues so I doubt this will be prioritized this year. Maybe we could get it looked at as a first pick, but we'd have to be pretty lucky.
Hello @Julesssss and @joekaufmanexpensify, may I inquire about my eligibility for payment? The reported bug has been confirmed as valid and subsequently fixed by our engineer. Initially, it was a deploy blocker in the first stage.
@tewodrosGirmaA My initial thought is I don't think any payment is due here. We did not fix anything in this issue. Generally the way we approach situations like this is you'd need to find the PR that fixed this to show that your report came first in order for this to qualify for payment.
If this was reported before whatever caused us to change this product behavior, LMK and I'll take another look!
Activity
OSBotify commentedon Aug 10, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Aug 10, 2023
Triggered auto assignment to @Julesssss (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.melvin-bot commentedon Aug 10, 2023
Triggered auto assignment to @joekaufmanexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Aug 10, 2023
Job added to Upwork: https://www.upwork.com/jobs/~01d88723e84c14ed1f
43 remaining items
joekaufmanexpensify commentedon Oct 9, 2023
Same.
joekaufmanexpensify commentedon Oct 16, 2023
Same
joekaufmanexpensify commentedon Oct 23, 2023
Same
joekaufmanexpensify commentedon Oct 30, 2023
@Julesssss do you think you'll be able to raise the fix for this one anytime soon?
Julesssss commentedon Oct 30, 2023
Sorry but no. All engineers are super busy with wave issues so I doubt this will be prioritized this year. Maybe we could get it looked at as a first pick, but we'd have to be pretty lucky.
joekaufmanexpensify commentedon Oct 30, 2023
Okay, all good. I will make it a monthly for now then!
Julesssss commentedon Nov 17, 2023
Hey @joekaufmanexpensify, I just retested this bug and I don't think it is occurring anymore 🎉
I see an updated preview. Would you mind verifying?
joekaufmanexpensify commentedon Nov 17, 2023
Sure, I'll take a look now!
joekaufmanexpensify commentedon Nov 17, 2023
Yep, this is fixed for me as well. Closing as no action needed in this issue!
tewodrosGirmaA commentedon Nov 17, 2023
Hello @Julesssss and @joekaufmanexpensify, may I inquire about my eligibility for payment? The reported bug has been confirmed as valid and subsequently fixed by our engineer. Initially, it was a deploy blocker in the first stage.
joekaufmanexpensify commentedon Nov 17, 2023
@tewodrosGirmaA My initial thought is I don't think any payment is due here. We did not fix anything in this issue. Generally the way we approach situations like this is you'd need to find the PR that fixed this to show that your report came first in order for this to qualify for payment.
If this was reported before whatever caused us to change this product behavior, LMK and I'll take another look!