Skip to content

[Hold PR #44907] [$250] Report field - Different system message for report field edit in expense report and LHN #44831

Closed

Description

@kavimuru

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.0.4-0
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory around https://expensify.testrail.io/index.php?/tests/view/4695978
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

Precondition:

  • User has created a Text type report field from Report fields section on ND.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses.
  4. Click on the text field.
  5. Enter text and save it.
  6. Revisit the expense report.

Expected Result:

The system message for report field edit will be consistent in expense report and LHN.

Actual Result:

The system message for report field edit is different in expense report and LHN.
In expense report, it shows "changed Text field from undefined to x."
In LHN, it shows "modified field 'Text field'. New value is 'x' (previously '').

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6533092_1720097340111.20240704_204417.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01d8549f82fbcaeb27
  • Upwork Job ID: 1808920292412937149
  • Last Price Increase: 2024-07-04

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jul 4, 2024
  2. melvin-bot commented on Jul 4, 2024

    @melvin-bot

    Triggered auto assignment to @arosiclair (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  3. melvin-bot commented on Jul 4, 2024

    @melvin-bot

    Triggered auto assignment to @trjExpensify (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.

  4. github-actions commented on Jul 4, 2024

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  5. arosiclair commented on Jul 4, 2024

    @arosiclair
    Contributor

    We can demote this per this thread (report fields are behind a beta).

  6. 23 remaining items

  7. melvin-bot commented on Jul 8, 2024

    @melvin-bot

    @arosiclair, @trjExpensify, @ZhenjaHorbach Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  8. changed the title [-][$250] Report field - Different system message for report field edit in expense report and LHN[/-] [+][Hold PR #44907] [$250] Report field - Different system message for report field edit in expense report and LHN[/+] on Jul 8, 2024
  9. trjExpensify commented on Jul 8, 2024

    @trjExpensify
    Contributor

    Cool, holding this issue. 👍

  10. trjExpensify commented on Jul 10, 2024

    @trjExpensify
    Contributor

    PR we're held on is in review.

  11. melvin-bot commented on Jul 10, 2024

    @melvin-bot

    @arosiclair, @trjExpensify, @ZhenjaHorbach Huh... This is 4 days overdue. Who can take care of this?

  12. arosiclair commented on Jul 11, 2024

    @arosiclair
    Contributor

    Not overdue

  13. arosiclair commented on Jul 15, 2024

    @arosiclair
    Contributor

    @trjExpensify should we just close this since it'll get fixed by the other issue?

  14. trjExpensify commented on Jul 15, 2024

    @trjExpensify
    Contributor

    Works for me, the PR for that has been deployed.

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributors

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions