[Due for payment 2025-03-21] [Back nav] Incorrect back navigation pressing Back

@quinthar

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

Version Number: 9.1.7-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation (hyperlinked to channel name): #quality

Action Performed:

Go to a room A
Switch to room B
Click on someone's avatar to open up their profile in the right pane
Click on Message to open that person's DM

Expected Result:

The detail is open in the right pane

Actual Result:

Return to room B

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @trjExpensify

@thienlnam

Triggered auto assignment to @thienlnam (AutoAssignerNewDotQuality)

@trjExpensify

Triggered auto assignment to @trjExpensify (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.

@WojtekBoman

Happy to take this one on with Wojtek cc @WojtekBoman can you please comment for assignment

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

@eVoloshchak

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

Fix navigating back to profile details when using message button #57756

If no regressions arise, payment will be issued on 2025-03-21. 🎊

For reference, here are some details about the assignees on this issue:

@eVoloshchak requires payment through NewDot Manual Requests
@WojtekBoman does not require payment (Contractor)

@eVoloshchak

@eVoloshchak @trjExpensify @eVoloshchak 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]

@eVoloshchak

Payment Summary

Upwork Job

Reviewer: @eVoloshchak owed $250 via NewDot
Contributor: @WojtekBoman is from an agency-contributor and not due payment

BugZero Checklist (@trjExpensify)

I have verified the correct assignees and roles are listed above and updated the necessary manual offers
I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
I have paid out the Upwork contracts or cancelled the ones that are incorrect
I have verified the payment summary above is correct

@eVoloshchak

👋 Checklist time, @eVoloshchak.

BugZero Checklist:

[Contributor] Classify the bug:

Bug classification

Source of bug:

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:

[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/45783/files#r2008046613
[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.

Regression wasn't CRITICAL
[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

Test:

Go to room A
Switch to room B
Click on someone's avatar to open up their profile in the right pane
Click on Message to open that person's DM
Go back
Verify if the profile details page has been opened

Do we agree 👍 or 👎

@eVoloshchak

Payment summary as follows:

$250 to @eVoloshchak for the C+ review

Go ahead and request. Closing!

@eVoloshchak

$250 approved for @eVoloshchak

Navigation Menu

Repository navigation

[Due for payment 2025-03-21] [Back nav] Incorrect back navigation pressing Back #57673

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

15 remaining items

Payment Summary

BugZero Checklist (@trjExpensify)

BugZero Checklist:

Regression Test Proposal

Test:

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Due for payment 2025-03-21] [Back nav] Incorrect back navigation pressing Back #57673

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

Activity

melvin-bot commented on Mar 3, 2025

melvin-bot commented on Mar 3, 2025

mountiny commented on Mar 3, 2025

15 remaining items

melvin-bot commented on Mar 14, 2025

melvin-bot commented on Mar 14, 2025

melvin-bot commented on Mar 14, 2025

melvin-bot commented on Mar 21, 2025

Payment Summary

BugZero Checklist (@trjExpensify)

trjExpensify commented on Mar 21, 2025

eVoloshchak commented on Mar 21, 2025

BugZero Checklist:

Regression Test Proposal

Test:

trjExpensify commented on Mar 24, 2025

garrettmknight commented on Dec 17, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions