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 2026-04-07] [$250] Update downgrade copy to be clearer #83318
Please re-state the problem that we are trying to solve in this issue.
Users who choose to downgrade from Control to Collect don't understand how this action impacts their specific workflow setup. The current downgrade modal copy is too vague and doesn't clearly explain which features they'll lose.
What is the root cause of that problem?
The translation strings for the downgrade modal in src/languages/en.ts use generic descriptions like "Accounting connections", "Smart expense rules", "Multi-level approval workflows", and "Enhanced security controls" — which don't give users enough detail about the specific features they'll lose.
Additionally, the rendering in src/pages/workspace/downgrade/DowngradeIntro.tsx treats all benefits as plain text strings without bold category labels, so there's no way to distinguish feature categories from their specific items.
What changes do you think we should make in order to solve the problem?
Update the translation strings in src/languages/en.ts (and other locale files) to use the new categorized copy:
downgrade: {
commonFeatures: {
- title: 'Downgrade to the Collect plan',- note: 'If you downgrade, you\'ll lose access to these features and more:',+ title: 'Downgrade to Collect',+ note: 'You\'ll lose access to the following features and more:',
benefits: {
note: 'For a full comparison of our plans, check out our',
pricingPage: 'pricing page',
- confirm: 'Are you sure you want to downgrade and remove your configurations?',- warning: 'This cannot be undone.',- benefit1: 'Accounting connections (except QuickBooks Online and Xero)',- benefit2: 'Smart expense rules',- benefit3: 'Multi-level approval workflows',- benefit4: 'Enhanced security controls',+ confirm: 'You\'ll need to change the "Plan type" of every workspace to "Collect" in order to secure the Collect rate.',+ benefit1Label: 'ERP integrations',+ benefit1: 'NetSuite, Sage Intacct, QuickBooks Desktop, Oracle, Microsoft Dynamics',+ benefit2Label: 'HR integrations',+ benefit2: 'Workday, Certinia',+ benefit3Label: 'Security',+ benefit3: 'SSO/SAML',+ benefit4Label: 'Advanced',+ benefit4: 'Smart expense rules, per diems, multi-level approvals, custom reporting, and budgeting',
Update src/pages/workspace/downgrade/DowngradeIntro.tsx to render benefits with bold category labels and update the IMPORTANT section:
Update the corresponding translations in all other locale files (nl.ts, pt-BR.ts, it.ts, de.ts, fr.ts, es.ts, ja.ts, zh-hans.ts, pl.ts).
What alternative solutions did you explore? (Optional)
We could use RenderHTML to render the benefits with inline bold styling from a single HTML string, but using structured data with separate label and value fields is cleaner, more maintainable, and consistent with the existing pattern in the codebase.
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
Please re-state the problem that we are trying to solve in this issue.
Users who choose to downgrade from Control to Collect don't understand how this action impacts their specific workflow setup. The current downgrade intro screen lists 4 generic features being lost ("Accounting connections", "Smart expense rules", "Multi-level approval workflows", "Enhanced security controls") without naming specific products or organizing them clearly.
What is the root cause of that problem?
The downgrade intro copy in DowngradeIntro.tsx uses 4 generic bullet points that don't clearly communicate the specific integrations and features users will lose. The translation strings at src/languages/en.ts:6220-6223 are vague:
Meanwhile, the Control plan already has a detailed feature list at src/languages/en.ts:7961-7974 that names specific products (NetSuite, Sage Intacct, Oracle, Workday, Certinia, etc.), but this information is not shown on the downgrade screen.
What changes do you think we should make in order to solve the problem?
Based on the Figma design, update the downgrade intro copy to use categorized, product-specific bullet points. The changes span 3 areas:
1. Update translation strings in src/languages/en.ts (lines 6211-6227):
Change title from "Downgrade to the Collect plan" → "Downgrade to Collect"
Change note from "If you downgrade, you'll lose access to these features and more:" → "You'll lose access to the following features and more:"
Replace the 4 generic benefit1-benefit4 strings with categorized entries matching the Figma:
ERP integrations: NetSuite, Sage Intacct, QuickBooks Desktop, Oracle, Microsoft Dynamics
HR integrations: Workday, Certinia
Security: SSO/SAML
Advanced: Smart expense rules, per diems, multi-level approvals, custom reporting, and budgeting
Replace the confirm/warning and headsUp/multiWorkspaceNote sections with a single important key: "IMPORTANT: You'll need to change the "Plan type" of every workspace to "Collect" in order to secure the Collect rate."
Remove the pricingPage and note keys (the pricing page link is removed from the body in the Figma design — "and more" in the description may serve as the link instead)
Update the benefits array (lines 34-39) to render the new categorized bullets. Each bullet needs a bold category label followed by normal-weight product names (e.g., <Text style={styles.textBold}>ERP integrations: </Text><Text>NetSuite, Sage Intacct...</Text>)
Replace the conditional policyID ? confirm/warning : headsUp/multiWorkspaceNote block (lines 72-85) with a single IMPORTANT callout that displays regardless of policyID
Remove the pricing page TextLink block (lines 62-71) since the Figma removes it from the body
Update the button section (lines 87-103): the Figma shows a single "Go to workspaces" button — evaluate whether the policyID conditional for the button should be simplified or kept for the single-workspace "Downgrade workspace" variant
3. Update all other language files (es.ts, pt-BR.ts, zh-hans.ts, ja.ts, nl.ts, pl.ts, fr.ts, it.ts, de.ts) with equivalent translations for the new keys.
What alternative solutions did you explore? (Optional)
An alternative would be to dynamically pull the feature list from the existing Control plan benefits (subscription.yourPlan.control.benefit1-8) rather than maintaining a separate set of downgrade-specific strings. However, the Figma design uses different groupings and wording (e.g., "ERP integrations" vs "ERP integrations (NetSuite, Sage Intacct, Oracle)"), so maintaining separate translation keys for the downgrade screen is the cleaner approach and matches the design exactly.
Relevant Code References
File
Lines
Purpose
src/pages/workspace/downgrade/DowngradeIntro.tsx
26-108
Main component rendering downgrade intro UI
src/languages/en.ts
6211-6234
English translation strings for downgrade copy
src/languages/en.ts
7961-7974
Control plan benefits (reference for feature names)
Please re-state the problem that we are trying to solve in this issue.
When users on the Control plan attempt to downgrade to Collect, the downgrade modal presents a generic, flat list of features they'll lose (e.g., "Accounting connections", "Smart expense rules", "Multi-level approval workflows", "Enhanced security controls") without enough specificity or structure, making it difficult for users to understand exactly how the downgrade will impact their workflow and which concrete integrations or capabilities they're giving up.
What is the root cause of that problem?
The DowngradeIntro component renders four generic benefit strings as a flat bullet list, with no categorization or specific product/integration names, so users can't map the listed features to their actual workflow setup.
The translation strings themselves are too vague — e.g., benefit1: 'Accounting connections (except QuickBooks Online and Xero)' doesn't tell the user which specific ERP/HR integrations they'll lose.
benefit1: 'Accounting connections (except QuickBooks Online and Xero)',
benefit2: 'Smart expense rules',
benefit3: 'Multi-level approval workflows',
benefit4: 'Enhanced security controls',
Additionally, the multi-workspace warning uses a "Heads up!" block that isn't prominent enough to convey the billing implication of needing to downgrade all workspaces.
What changes do you think we should make in order to solve the problem?
Update the translation strings in en.ts (and es.ts) to replace the four generic benefits with structured, category-labeled items that name specific products, and update the note/title copy to match the Figma design.
note: 'If you downgrade, you’ll lose access to these features and more:',
benefits: {
note: 'For a full comparison of our plans, check out our',
pricingPage: 'pricing page',
confirm: 'Are you sure you want to downgrade and remove your configurations?',
warning: 'This cannot be undone.',
benefit1: 'Accounting connections (except QuickBooks Online and Xero)',
benefit2: 'Smart expense rules',
benefit3: 'Multi-level approval workflows',
benefit4: 'Enhanced security controls',
headsUp: 'Heads up!',
multiWorkspaceNote: 'You’ll need to downgrade all your workspaces before your first monthly payment to begin a subscription at the Collect rate. Click',
selectStep: '> select each workspace > change the plan type to',
},
--- a/src/languages/en.ts+++ b/src/languages/en.ts@@ -6211,17 +6211,14 @@
downgrade: {
commonFeatures: {
- title: 'Downgrade to the Collect plan',- note: 'If you downgrade, you'll lose access to these features and more:',+ title: 'Downgrade to Collect',+ note: "You'll lose access to the following features ",+ andMore: 'and more',
benefits: {
- note: 'For a full comparison of our plans, check out our',- pricingPage: 'pricing page',
confirm: 'Are you sure you want to downgrade and remove your configurations?',
warning: 'This cannot be undone.',
- benefit1: 'Accounting connections (except QuickBooks Online and Xero)',- benefit2: 'Smart expense rules',- benefit3: 'Multi-level approval workflows',- benefit4: 'Enhanced security controls',+ benefit1: 'ERP integrations: NetSuite, Sage Intacct, QuickBooks Desktop, Oracle, Microsoft Dynamics',+ benefit2: 'HR integrations: Workday, Certinia',+ benefit3: 'Security: SSO/SAML',+ benefit4: 'Advanced: Smart expense rules, per diems, multi-level approvals, custom reporting, and budgeting',
headsUp: 'Heads up!',
- multiWorkspaceNote: 'You'll need to downgrade all your workspaces before your first monthly payment to begin a subscription at the Collect rate. Click',- selectStep: '> select each workspace > change the plan type to',+ important: 'IMPORTANT: You\'ll need to change the "Plan type" of every workspace to "Collect" in order to secure the Collect rate.',
},
},
Update the DowngradeIntro component to render the new structured copy — make "and more" a link to the pricing page, render benefits with bold category labels (text before the colon), and replace the multi-workspace warning with the new IMPORTANT: text.
note: 'Si desmejoras, perderás acceso a estas funciones y más:',
benefits: {
note: 'Para una comparación completa de nuestros planes, consulta nuestra',
pricingPage: 'página de precios',
confirm: '¿Estás seguro de que deseas desmejorar y eliminar tus configuraciones?',
warning: 'Esto no se puede deshacer.',
benefit1: 'Conexiones de contabilidad (excepto QuickBooks Online y Xero)',
benefit2: 'Reglas inteligentes de gastos',
benefit3: 'Flujos de aprobación de varios niveles',
benefit4: 'Controles de seguridad mejorados',
headsUp: '¡Atención!',
multiWorkspaceNote:
'Tendrás que bajar de categoría todos tus espacios de trabajo antes de tu primer pago mensual para comenzar una suscripción con la tasa del plan Recopilar. Haz clic en',
selectStep: '> selecciona cada espacio de trabajo > cambia el tipo de plan a',
},
--- a/src/languages/es.ts+++ b/src/languages/es.ts@@ -6082,17 +6082,14 @@
downgrade: {
commonFeatures: {
- title: 'Desmejorar al plan Recopilar',- note: 'Si desmejoras, perderás acceso a estas funciones y más:',+ title: 'Desmejorar a Recopilar',+ note: 'Perderás acceso a las siguientes funciones ',+ andMore: 'y más',
benefits: {
- note: 'Para una comparación completa de nuestros planes, consulta nuestra',- pricingPage: 'página de precios',
confirm: '¿Estás seguro de que deseas desmejorar y eliminar tus configuraciones?',
warning: 'Esto no se puede deshacer.',
- benefit1: 'Conexiones de contabilidad (excepto QuickBooks Online y Xero)',- benefit2: 'Reglas inteligentes de gastos',- benefit3: 'Flujos de aprobación de varios niveles',- benefit4: 'Controles de seguridad mejorados',+ benefit1: 'Integraciones ERP: NetSuite, Sage Intacct, QuickBooks Desktop, Oracle, Microsoft Dynamics',+ benefit2: 'Integraciones de RRHH: Workday, Certinia',+ benefit3: 'Seguridad: SSO/SAML',+ benefit4: 'Avanzado: Reglas inteligentes de gastos, viáticos, aprobaciones multinivel, informes personalizados y presupuestos',
headsUp: '¡Atención!',
- multiWorkspaceNote: '...',- selectStep: '...',+ important: 'IMPORTANTE: Deberás cambiar el "Tipo de plan" de cada espacio de trabajo a "Recopilar" para asegurar la tarifa de Recopilar.',
},
},
Update the header title from "Downgrade workspace" to "Downgrade this workspace" in en.ts (and corresponding translations) to match the Figma.
note: 'If you downgrade, you’ll lose access to these features and more:',
benefits: {
note: 'For a full comparison of our plans, check out our',
pricingPage: 'pricing page',
confirm: 'Are you sure you want to downgrade and remove your configurations?',
warning: 'This cannot be undone.',
benefit1: 'Accounting connections (except QuickBooks Online and Xero)',
benefit2: 'Smart expense rules',
benefit3: 'Multi-level approval workflows',
benefit4: 'Enhanced security controls',
headsUp: 'Heads up!',
multiWorkspaceNote: 'You’ll need to downgrade all your workspaces before your first monthly payment to begin a subscription at the Collect rate. Click',
selectStep: '> select each workspace > change the plan type to',
note: (moreMethodsRoute: string)=>`You’ll lose access to the following features <a href="${moreMethodsRoute}">and more</a>`,
What alternative solutions did you explore? (Optional)
Result:
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
changed the title [-][$250] Update downgrade copy to be clearer[/-][+][Due for payment 2026-04-07] [$250] Update downgrade copy to be clearer[/+]on Mar 31, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.50-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@aimane-chnaif 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] 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: No regression. Just copy change
[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:
[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 Feb 24, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @aimane-chnaif (
External)melvin-bot commentedon Feb 24, 2026
Current assignee @dylanexpensify is eligible for the Bug assigner, not assigning anyone new.
[-]Update downgrade copy to be clearer[/-][+][$250] Update downgrade copy to be clearer[/+]melvin-bot commentedon Feb 24, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022026259494234506823
daledah commentedon Feb 24, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
Users who choose to downgrade from Control to Collect don't understand how this action impacts their specific workflow setup. The current downgrade modal copy is too vague and doesn't clearly explain which features they'll lose.
What is the root cause of that problem?
The translation strings for the downgrade modal in
src/languages/en.tsuse generic descriptions like "Accounting connections", "Smart expense rules", "Multi-level approval workflows", and "Enhanced security controls" — which don't give users enough detail about the specific features they'll lose.Additionally, the rendering in
src/pages/workspace/downgrade/DowngradeIntro.tsxtreats all benefits as plain text strings without bold category labels, so there's no way to distinguish feature categories from their specific items.What changes do you think we should make in order to solve the problem?
src/languages/en.ts(and other locale files) to use the new categorized copy:downgrade: { commonFeatures: { - title: 'Downgrade to the Collect plan', - note: 'If you downgrade, you\'ll lose access to these features and more:', + title: 'Downgrade to Collect', + note: 'You\'ll lose access to the following features and more:', benefits: { note: 'For a full comparison of our plans, check out our', pricingPage: 'pricing page', - confirm: 'Are you sure you want to downgrade and remove your configurations?', - warning: 'This cannot be undone.', - benefit1: 'Accounting connections (except QuickBooks Online and Xero)', - benefit2: 'Smart expense rules', - benefit3: 'Multi-level approval workflows', - benefit4: 'Enhanced security controls', + confirm: 'You\'ll need to change the "Plan type" of every workspace to "Collect" in order to secure the Collect rate.', + benefit1Label: 'ERP integrations', + benefit1: 'NetSuite, Sage Intacct, QuickBooks Desktop, Oracle, Microsoft Dynamics', + benefit2Label: 'HR integrations', + benefit2: 'Workday, Certinia', + benefit3Label: 'Security', + benefit3: 'SSO/SAML', + benefit4Label: 'Advanced', + benefit4: 'Smart expense rules, per diems, multi-level approvals, custom reporting, and budgeting',src/pages/workspace/downgrade/DowngradeIntro.tsxto render benefits with bold category labels and update the IMPORTANT section:nl.ts,pt-BR.ts,it.ts,de.ts,fr.ts,es.ts,ja.ts,zh-hans.ts,pl.ts).What alternative solutions did you explore? (Optional)
We could use
RenderHTMLto render the benefits with inline bold styling from a single HTML string, but using structured data with separatelabelandvaluefields is cleaner, more maintainable, and consistent with the existing pattern in the codebase.Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
MelvinBot commentedon Feb 24, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
Users who choose to downgrade from Control to Collect don't understand how this action impacts their specific workflow setup. The current downgrade intro screen lists 4 generic features being lost ("Accounting connections", "Smart expense rules", "Multi-level approval workflows", "Enhanced security controls") without naming specific products or organizing them clearly.
What is the root cause of that problem?
The downgrade intro copy in
DowngradeIntro.tsxuses 4 generic bullet points that don't clearly communicate the specific integrations and features users will lose. The translation strings atsrc/languages/en.ts:6220-6223are vague:Meanwhile, the Control plan already has a detailed feature list at
src/languages/en.ts:7961-7974that names specific products (NetSuite, Sage Intacct, Oracle, Workday, Certinia, etc.), but this information is not shown on the downgrade screen.What changes do you think we should make in order to solve the problem?
Based on the Figma design, update the downgrade intro copy to use categorized, product-specific bullet points. The changes span 3 areas:
1. Update translation strings in
src/languages/en.ts(lines 6211-6227):titlefrom "Downgrade to the Collect plan" → "Downgrade to Collect"notefrom "If you downgrade, you'll lose access to these features and more:" → "You'll lose access to the following features and more:"benefit1-benefit4strings with categorized entries matching the Figma:confirm/warningandheadsUp/multiWorkspaceNotesections with a singleimportantkey: "IMPORTANT: You'll need to change the "Plan type" of every workspace to "Collect" in order to secure the Collect rate."pricingPageandnotekeys (the pricing page link is removed from the body in the Figma design — "and more" in the description may serve as the link instead)2. Update
DowngradeIntro.tsx(src/pages/workspace/downgrade/DowngradeIntro.tsx):benefitsarray (lines 34-39) to render the new categorized bullets. Each bullet needs a bold category label followed by normal-weight product names (e.g.,<Text style={styles.textBold}>ERP integrations: </Text><Text>NetSuite, Sage Intacct...</Text>)policyID ? confirm/warning : headsUp/multiWorkspaceNoteblock (lines 72-85) with a single IMPORTANT callout that displays regardless of policyIDTextLinkblock (lines 62-71) since the Figma removes it from the bodypolicyIDconditional for the button should be simplified or kept for the single-workspace "Downgrade workspace" variant3. Update all other language files (
es.ts,pt-BR.ts,zh-hans.ts,ja.ts,nl.ts,pl.ts,fr.ts,it.ts,de.ts) with equivalent translations for the new keys.What alternative solutions did you explore? (Optional)
An alternative would be to dynamically pull the feature list from the existing Control plan benefits (
subscription.yourPlan.control.benefit1-8) rather than maintaining a separate set of downgrade-specific strings. However, the Figma design uses different groupings and wording (e.g., "ERP integrations" vs "ERP integrations (NetSuite, Sage Intacct, Oracle)"), so maintaining separate translation keys for the downgrade screen is the cleaner approach and matches the design exactly.Relevant Code References
src/pages/workspace/downgrade/DowngradeIntro.tsxsrc/languages/en.tssrc/languages/en.tssrc/pages/workspace/downgrade/WorkspaceDowngradePage.tsxsrc/pages/workspace/downgrade/DowngradeConfirmation.tsxNext Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR, or@MelvinBot <your feedback>to refine this analysis.mukhrr commentedon Feb 24, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
When users on the Control plan attempt to downgrade to Collect, the downgrade modal presents a generic, flat list of features they'll lose (e.g., "Accounting connections", "Smart expense rules", "Multi-level approval workflows", "Enhanced security controls") without enough specificity or structure, making it difficult for users to understand exactly how the downgrade will impact their workflow and which concrete integrations or capabilities they're giving up.
What is the root cause of that problem?
The
DowngradeIntrocomponent renders four generic benefit strings as a flat bullet list, with no categorization or specific product/integration names, so users can't map the listed features to their actual workflow setup.App/src/pages/workspace/downgrade/DowngradeIntro.tsx
Lines 34 to 39 in 8af1e14
The translation strings themselves are too vague — e.g.,
benefit1: 'Accounting connections (except QuickBooks Online and Xero)'doesn't tell the user which specific ERP/HR integrations they'll lose.App/src/languages/en.ts
Lines 6220 to 6223 in 8af1e14
Additionally, the multi-workspace warning uses a "Heads up!" block that isn't prominent enough to convey the billing implication of needing to downgrade all workspaces.
App/src/pages/workspace/downgrade/DowngradeIntro.tsx
Lines 72 to 85 in 8af1e14
What changes do you think we should make in order to solve the problem?
en.ts(andes.ts) to replace the four generic benefits with structured, category-labeled items that name specific products, and update the note/title copy to match the Figma design.App/src/languages/en.ts
Lines 6211 to 6227 in 8af1e14
DowngradeIntrocomponent to render the new structured copy — make "and more" a link to the pricing page, render benefits with bold category labels (text before the colon), and replace the multi-workspace warning with the newIMPORTANT:text.App/src/pages/workspace/downgrade/DowngradeIntro.tsx
Lines 41 to 105 in 8af1e14
es.tswith the corresponding Spanish translations for the new copy, mirroring the same structural changes.App/src/languages/es.ts
Lines 6082 to 6099 in 8af1e14
en.ts(and corresponding translations) to match the Figma.App/src/languages/en.ts
Line 441 in 8af1e14
PiyushChandra17 commentedon Feb 24, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
Update downgrade copy to be clearer
What is the root cause of that problem?
Copy Update
What changes do you think we should make in order to solve the problem?
App/src/pages/workspace/downgrade/DowngradeIntro.tsx
Lines 34 to 39 in 22ecc4d
App/src/pages/workspace/downgrade/DowngradeIntro.tsx
Lines 51 to 85 in 22ecc4d
en.ts&&es.ts&& all for all language locales hereApp/src/languages/en.ts
Lines 6211 to 6228 in 22ecc4d
Notehere:App/src/languages/en.ts
Line 6214 in 22ecc4d
We can use
RenderHTMLto translate instead ofTextcomponent whereand morewould be thelinkWhat alternative solutions did you explore? (Optional)
Result:
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
35 remaining items
[-][$250] Update downgrade copy to be clearer[/-][+][Due for payment 2026-04-07] [$250] Update downgrade copy to be clearer[/+]melvin-bot commentedon Mar 31, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 31, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.50-8 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 2026-04-07. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 31, 2026
@aimane-chnaif 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]
melvin-bot commentedon Mar 31, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon Apr 8, 2026
Payment Summary
Contributor: @daledah due $250 via NewDot
Contributor+: @aimane-chnaif paid $250 via Upwork
@aimane-chnaif plz complete the BZ checklist and tag me in a post once you have. Thx
aimane-chnaif commentedon Apr 8, 2026
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: No regression. Just copy change
[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:
[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/622214
Regression Test Proposal
Precondition
The user has a control workspace
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-c694-acf0-cbd9-0dc71c2ce804quinthar commentedon May 12, 2026
Approved $250 for @daledah