Skip to content

Request Money -The word "Request" in the conversation appears with a small letter #18359

Closed

Description

@kbecciv

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


Action Performed:

  1. Go to URL https://staging.new.expensify.com/
  2. Login with any account
  3. Navigate to a conversation
  4. Click on the + button in the compose box and select Request Money.

Expected Result:

The word "Request" must be displayed in capital letter.

Actual Result:

The word "Request" in the conversation appears with a small letter.

Workaround:

Unknown

Platforms:

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

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.9.14

Reproducible in staging?: yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

Bug6041541_Recording__2375.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 3, 2023
  2. MelvinBot commented on May 3, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @sophiepintoraetz (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. MelvinBot commented on May 3, 2023

    @MelvinBot
    Contributor

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. added
    DeployBlockerCashThis issue or pull request should block deployment
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 3, 2023
  5. OSBotify commented on May 3, 2023

    @OSBotify
    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.
  6. MelvinBot commented on May 3, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @dangrous (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  7. marcaaron commented on May 3, 2023

    @marcaaron
    Contributor

    asking @luacmartins to check this one out I believe he has the most context

  8. dangrous commented on May 3, 2023

    @dangrous
    Contributor

    Yeah basically do we need to update the optimistic data, or do we need to adjust the backend to send a capital letter again? I see it was an intentional choice - https://github.com/Expensify/Web-Expensify/pull/37076/commits/ced6a21b3dca719510fda6e9b290543843e5aed2 - but wondering where that comes from?

    (and if we update the optimistic data to match, we should also update whatever TestRail it is that says all of these should be capitalized)

  9. marcaaron commented on May 3, 2023

    @marcaaron
    Contributor

    Ah Carlos M is ooo actually. Let's ask in eng chat.

  10. marcaaron commented on May 3, 2023

    @marcaaron
    Contributor

    There might also be a plan to update app or an open PR... maybe we just chose to roll out Web first then fix App later.

  11. luacmartins commented on May 3, 2023

    @luacmartins
    Contributor

    This is the expected behavior. We are updating to lower case letters. I have an app PR in review that addresses that.

  12. luacmartins commented on May 3, 2023

    @luacmartins
    Contributor

    Closing this issue since it’s the expected behavior

  13. marcaaron commented on May 3, 2023

    @marcaaron
    Contributor

    Reopening for a second... the expected behavior is for the message to change from capitalized to not capitalized?

  14. marcaaron commented on May 3, 2023

    @marcaaron
    Contributor
  15. dangrous commented on May 3, 2023

    @dangrous
    Contributor

    The optimistic data shall be fixed soon! https://github.com/Expensify/App/pull/17583/files

    @kbecciv do you have test steps that specify the capital letter Requested? We'll need to update those, as it will be shifting to always lowercase requested. Thank you!

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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions