Skip to content

[Due for payment 2025-11-06] [$50] Update Constant for View payment history #73140

Closed

Description

@danielrvidal

If you click View payment history in users accounts, it does always show you all your Expensify charges because the constant is to search for "Expensify, Inc." but at some point we were setting the merchant to "Expensify". So we need to update the search constant to just look for "Expensify" so it will show both versions.

Image
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021980688327515653404
  • Upwork Job ID: 1980688327515653404
  • Last Price Increase: 2025-10-21
  • Automatic offers:
    • FitseTLT | Reviewer | 109197687
    • mkzie2 | Contributor | 109197690
Issue OwnerCurrent Issue Owner: @mkzie2

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Oct 21, 2025
  2. changed the title [-]Update Constant for View payment history[/-] [+][$250] Update Constant for View payment history[/+] on Oct 21, 2025
  3. melvin-bot commented on Oct 21, 2025

    @melvin-bot
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Oct 21, 2025
  5. melvin-bot commented on Oct 21, 2025

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @FitseTLT (External)

  6. changed the title [-][$250] Update Constant for View payment history[/-] [+][$50] Update Constant for View payment history[/+] on Oct 21, 2025
  7. melvin-bot commented on Oct 21, 2025

    @melvin-bot

    ⚠️ Failed to update price automatically. The BZ team member will need to update the price manually in Upwork.

  8. mkzie2 commented on Oct 21, 2025

    @mkzie2
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Update Constant for View payment history

    What is the root cause of that problem?

    We set it here

    EXPENSIFY_MERCHANT: 'Expensify, Inc.',

    What changes do you think we should make in order to solve the problem?

    Correct the value

    What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

    NA

    What alternative solutions did you explore? (Optional)

    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.

  9. github-actions commented on Oct 21, 2025

    @github-actions
    Contributor

    ⚠️ @mkzie2 Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

  10. github-actions commented on Oct 21, 2025

    @github-actions
    Contributor

    ⚠️ @daledah Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

  11. 27 remaining items

  12. FitseTLT commented on Nov 25, 2025

    @FitseTLT
    Contributor

    @RachCHopkins Payments here

  13. melvin-bot commented on Dec 1, 2025

    @melvin-bot

    This issue has not been updated in over 14 days. @luacmartins, @RachCHopkins, @FitseTLT, @mkzie2 eroding to Weekly issue.

  14. melvin-bot commented on Dec 25, 2025

    @melvin-bot

    This issue has not been updated in over 15 days. @luacmartins, @RachCHopkins, @FitseTLT, @mkzie2 eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  15. mallenexpensify commented on Dec 29, 2025

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @mkzie2 paid $50 via Upwork
    Contributor+: @FitseTLT paid $50 via Upwork

    I don't think we need a test case here, comment/reopen if ya disagree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions