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-12-04] [$250] Upgrade Option Has Incorrect Amount Listed #75340
Version Number: v9.2.55-3
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers): cortney@expensify.com
Issue reported by: @CortneyOfstad
Device used: Web
App Component: Workspace Settings
Action Performed:
Open expense
Click on associated Report
get pop-up message "Upgrade, unlock this feature."
Expected Result:
The text should read $5, not $9 when updating from Free to Collect
Please re-state the problem that we are trying to solve in this issue.
When a Free user taps an expense’s associated report, the upgrade modal shows the Collect plan at $9/month instead of the correct $5/month.
What is the root cause of that problem?
The upgrade intro view picks the corporate (Control) annual price unless the flow is categorizing or distance-rate related, so the reporting upgrade path falls through to the higher $9 price.
changed the title [-][$250] Upgrade Option Has Incorrect Amount Listed[/-][+][Due for payment 2025-12-04] [$250] Upgrade Option Has Incorrect Amount Listed[/+]on Nov 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.64-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@dukenv0307@CortneyOfstad 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]
[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: New requirement
[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.
Activity
CortneyOfstad commentedon Nov 17, 2025
Originally created under the Expensify/Expensify repo after an SRAM reported the issue. QA was able to recreate here
[-]Upgrade Option Has Incorrect Amount Listed[/-][+][$250] Upgrade Option Has Incorrect Amount Listed[/+]melvin-bot commentedon Nov 17, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021990498183073560547
melvin-bot commentedon Nov 17, 2025
Current assignee @CortneyOfstad is eligible for the Bug assigner, not assigning anyone new.
melvin-bot commentedon Nov 17, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (
External)ShridharGoel commentedon Nov 17, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
When a Free user taps an expense’s associated report, the upgrade modal shows the Collect plan at $9/month instead of the correct $5/month.
What is the root cause of that problem?
The upgrade intro view picks the corporate (Control) annual price unless the flow is categorizing or distance-rate related, so the reporting upgrade path falls through to the higher $9 price.
App/src/pages/workspace/upgrade/UpgradeIntro.tsx
Lines 48 to 55 in 4c1d026
What changes do you think we should make in order to solve the problem?
Treat the reporting upgrade path like categorizing/distance upgrades by using the team (Collect) pricing when formatting the upgrade price.
Updated code snippet:
We can check if there are some other scenarios also which should use the Collect pricing.
PiyushChandra17 commentedon Nov 17, 2025
🚨 Edited by proposal-police: This proposal was edited at 2025-11-17 20:28:19 UTC.
Proposal
Please re-state the problem that we are trying to solve in this issue.
Upgrade Option Has Incorrect Amount Listed
What is the root cause of that problem?
Subscription Price Update
What changes do you think we should make in order to solve the problem?
We are setting the amount listed in
formattedPricehereIn upgrade into page, we are setting the
formattedPricelogic in useMemo block here, the price value comes from CONST.SUBSCRIPTION_PRICESWe need to update the SUBSCRIPTION_PRICES > USD > corporate > yearly2018: 500 here
What alternative solutions did you explore? (Optional)
n/A
Result
dukenv0307 commentedon Nov 18, 2025
@ShridharGoel @PiyushChandra17 Do you guys know how to reproduce?
PiyushChandra17 commentedon Nov 18, 2025
@dukenv0307 Yes,
17 remaining items
[-][$250] Upgrade Option Has Incorrect Amount Listed[/-][+][Due for payment 2025-12-04] [$250] Upgrade Option Has Incorrect Amount Listed[/+]melvin-bot commentedon Nov 27, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 27, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.64-5 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-12-04. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 27, 2025
@dukenv0307 @CortneyOfstad 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]
CortneyOfstad commentedon Dec 1, 2025
@dukenv0307 — can you complete the checklist before the payment date so there is no risk of delay? Thanks!
dukenv0307 commentedon Dec 2, 2025
BugZero Checklist:
[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/54340/files#r2581272117
[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: New requirement
[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 👎
dukenv0307 commentedon Dec 2, 2025
@CortneyOfstad I completed, thank you
CortneyOfstad commentedon Dec 4, 2025
Payment Summary
@ShridharGoel — to be paid $250 via NewDot
@dukenv0307 — to be paid $250 via NewDot
Regression Test
https://github.com/Expensify/Expensify/issues/574581
twisterdotcom commentedon Dec 8, 2025
@ShridharGoel has submitted payment for this report on ND here.
SO: https://stackoverflowteams.com/c/expensify/questions/7582
Zapier Logs
Run ID: 00040eee-c469-aa1f-9c7e-22b950099bb4quinthar commentedon Dec 19, 2025
Approved $250 to @dukenv0307