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
[HOLD for payment 2024-08-02] Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page #45864
Version Number: 9.0.10-2 Reproducible in staging?: Y Reproducible in production?: N If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team
Action Performed:
Precondition:
Billable feature is enabled on Old Dot.
Go to staging.new.expensify.com
Go to workspace chat
Submit two expenses - Both have the same amount and merchant, but one has enabled billable toggle and the other has disabled billable toggle
Go to transaction thread of the expense that has disabled billable option
Click Review duplicates
Select Keep this one (any)
On "Choose if transaction is billable", select Yes.8. Proceed to confirmation page
Expected Result:
Billable toggle should be enabled as user has chosen Yes on "Choose if transaction is billable" step
Actual Result:
Billable toggle remains disabled on confirmation page when user has chosen Yes on "Choose if transaction is billable" step
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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.
@yuwenmemon I am reassigning the issue to myself so I can review and track the fixes since this is for the duplicate detection project that I am handling.
changed the title [-]Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page[/-][+][HOLD for payment 2024-08-02] Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page[/+]on Jul 26, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@pecanoro] The PR that introduced the bug has been identified. Link to the PR:
[@pecanoro] 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:
[@pecanoro] A discussion in #expensify-bugs 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:
[@pecanoro] Determine if we should create a regression test for this bug.
[@pecanoro] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@JmillsExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
Activity
melvin-bot commentedon Jul 21, 2024
Triggered auto assignment to @yuwenmemon (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 21, 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:
dominictb commentedon Jul 22, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
App/src/components/ReportActionItem/MoneyRequestView.tsx
Line 635 in f3a8f73
we do not use the
billabledata fromupdatedTransactionWhat changes do you think we should make in order to solve the problem?
mountiny commentedon Jul 22, 2024
The dupe detection is behind beta so we can demote
@JmillsExpensify @pecanoro @kubabutkiewicz @parasharrajat
parasharrajat commentedon Jul 22, 2024
@kubabutkiewicz Let's fix this on your PR.
pecanoro commentedon Jul 22, 2024
@yuwenmemon I am reassigning the issue to myself so I can review and track the fixes since this is for the duplicate detection project that I am handling.
13 remaining items
[-]Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page[/-][+][HOLD for payment 2024-08-02] Dupe detect - Billable toggle on confirm page does not reflect the selection on discrepancy page[/+]melvin-bot commentedon Jul 26, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 26, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 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 2024-08-02. 🎊
melvin-bot commentedon Jul 26, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
melvin-bot commentedon Aug 2, 2024
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
melvin-bot commentedon Aug 6, 2024
@JmillsExpensify, @pecanoro Eep! 4 days overdue now. Issues have feelings too...
JmillsExpensify commentedon Aug 7, 2024
Payment is being handled in another issue, so going to close this one out.