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-02-28] Selection gets removed after navigating to a single per diem option #54498
Version Number: 9.0.78-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):applausetester+nl895@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Windows 11 pro/chrome App Component: Workspace Settings
Action Performed:
Navigate to staging.new.expensify.com
Create a workspace
Enable per diem
Import a spreadsheet for per diem
Select all
Click on one of the per diem rates
Expected Result:
Selection doesn't reset. (App works consistently with the categories page)
👋 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.
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: I wasn't able to pinpoint the exact PR which caused this. Seemed like this was an issue since the start of this feature.
[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.
Activity
melvin-bot commentedon Dec 24, 2024
Triggered auto assignment to @grgia (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 24, 2024
Triggered auto assignment to @Christinadobrzyn (
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 Dec 24, 2024
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 24, 2024
👋 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:
NJ-2020 commentedon Dec 24, 2024
I think this could be NAB because in this issue we're only fixing for categories page only
If we want to fix inside the per-diem page also, we can do the same as we do for categories page
jasperhuangg commentedon Dec 24, 2024
@truph01 Care to take on this issue as well?
55 remaining items
Christinadobrzyn commentedon Feb 24, 2025
Ah thank you! @allroundexperts should we have a regression test for this?
melvin-bot commentedon Feb 28, 2025
Payment Summary
Upwork Job
BugZero Checklist (@Christinadobrzyn)
allroundexperts commentedon Mar 3, 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: I wasn't able to pinpoint the exact PR which caused this. Seemed like this was an issue since the start of this feature.
[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: https://github.com/Expensify/Expensify/issues/476310
Regression Test Proposal
Precondition:
Test:
Verify that the selection doesn't reset.
Do we agree 👍 or 👎
Christinadobrzyn commentedon Mar 3, 2025
Regression test - https://github.com/Expensify/Expensify/issues/476310
Payment summary here - #54498 (comment)
Closing as complete, @allroundexperts please make sure to submit a payment request in New Expensify. thanks!
JmillsExpensify commentedon Jun 13, 2025
$250 approved for @allroundexperts