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
[Due for payment 2025-06-02] [$250] Tap back button on detail expense if deleting expense should return to Workspace chat #62075
Version Number: 9.1.45-18 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:#60292 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Android 13 / Xiaomi Poco F5, iOS 15.8.3 / iPhone 7 Plus, Chrome / Android 13 App Component: Other
Action Performed:
Log in with a Gmail account
Open any workspace/1-1 chat
Submit two expenses
Open the detail expense of any expense
Tap the More button and tap Delete
Tap Delete again on the confirmation modal
Tap the app back button on the expense detail
Expected Result:
Tap the back button on the detail expense after delete expense should return to the Workspace chat
Actual Result:
Tap the back button on the detail expense after deleting the expense will navigate to the detail expense again
👋 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.
changed the title [-][$250] Tap back button on detail expense if deleting expense should return to Workspace chat[/-][+][Due for payment 2025-06-02] [$250] Tap back button on detail expense if deleting expense should return to Workspace chat[/+]on May 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@allroundexperts@isabelastisser@allroundexperts The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
N/A
Test:
Log in with a Gmail account
Open any workspace/1-1 chat
Submit two expenses
Open the detail expense of any expense
Tap the More button and tap Delete
Tap Delete again on the confirmation modal
Tap the app back button on the expense detail
Make sure that you are redirected to the workspace chat.
Activity
melvin-bot commentedon May 15, 2025
Triggered auto assignment to @isabelastisser (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon May 15, 2025
Triggered auto assignment to @MariaHCD (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon May 15, 2025
👋 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:
melvin-bot commentedon May 15, 2025
💬 A slack conversation has been started in #expensify-open-source
PiyushChandra17 commentedon May 15, 2025
Working on this one :)
MariaHCD commentedon May 15, 2025
👋🏼 @PiyushChandra17 we haven't made this external yet 🤔
MariaHCD commentedon May 15, 2025
@VickyStash looks like your PR was reverted and you're working on a new one here: #62080
Is this bug related to your changes in the original PR? If so, is it something that will be fixed in your new PR? :)
32 remaining items
[-][$250] Tap back button on detail expense if deleting expense should return to Workspace chat[/-][+][Due for payment 2025-06-02] [$250] Tap back button on detail expense if deleting expense should return to Workspace chat[/+]melvin-bot commentedon May 26, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 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 2025-06-02. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 26, 2025
@allroundexperts @isabelastisser @allroundexperts The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
isabelastisser commentedon May 28, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment:
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
isabelastisser commentedon May 28, 2025
@allroundexperts, please complete the BZ checklist, thanks!
allroundexperts commentedon Jun 1, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/59999/files#r2119598535
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion: N/A
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Make sure that you are redirected to the workspace chat.
Do we agree 👍 or 👎
melvin-bot commentedon Jun 2, 2025
Payment Summary
Upwork Job
BugZero Checklist (@isabelastisser)
isabelastisser commentedon Jun 2, 2025
Payment summary:
Reviewer: @allroundexperts owed $250 via NewDot for c+ review
pendingJmillsExpensify commentedon Jun 13, 2025
$250 approved for @allroundexperts