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
Version Number: 9.2.64-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#72943 Email or phone of affected tester (no customers):sdjnosdnjonsijndsodsjo@gmail.com Issue reported by: Applause Internal Team Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create three expenses with different amount and category (category should not in alphabetical order).
Open the expense report.
Open the first expense.
Navigate through the expenses with arrow on the top right.
Expected Result:
Navigation via arrows should sync with the order of expenses in the expense report.
Actual Result:
Navigation via arrows does not sync with the order of expenses in the expense report.
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.2.64-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #72943
Email or phone of affected tester (no customers): sdjnosdnjonsijndsodsjo@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.1 / Chrome
App Component: Money Requests
Action Performed:
Expected Result:
Navigation via arrows should sync with the order of expenses in the expense report.
Actual Result:
Navigation via arrows does not sync with the order of expenses in the expense report.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug7013708_1764125130701.7.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @kadiealexander