Skip to content

[HOLD for payment 2024-03-07] Hold dot separator doesn’t show in the expense preview #36977

Description

@robertjchen

Action Performed:

Go to Expense preview for held request

Expected Result:

image

Actual Result:

image

Workaround:

N/A

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

See above

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 20, 2024
  2. self-assigned this
    on Feb 20, 2024
  3. melvin-bot commented on Feb 20, 2024

    @melvin-bot

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

  4. melvin-bot commented on Feb 26, 2024

    @melvin-bot

    @robertjchen Eep! 4 days overdue now. Issues have feelings too...

  5. robertjchen commented on Feb 26, 2024

    @robertjchen
    ContributorAuthor

    Finalizing PR

  6. added
    ReviewingHas a PR in review
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 26, 2024
  7. changed the title [-]Hold dot separator doesn’t show in the expense preview[/-] [+][HOLD for payment 2024-03-07] Hold dot separator doesn’t show in the expense preview[/+] on Feb 29, 2024
  8. melvin-bot commented on Feb 29, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  9. melvin-bot commented on Feb 29, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.45-6 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 2024-03-07. 🎊

  10. melvin-bot commented on Feb 29, 2024

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@robertjchen] The PR that introduced the bug has been identified. Link to the PR:
    • [@robertjchen] 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:
    • [@robertjchen] A discussion in #expensify-bugs 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:
    • [@robertjchen] Determine if we should create a regression test for this bug.
    • [@robertjchen] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
    • [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  11. situchan commented on Mar 6, 2024

    @situchan
    Contributor

    C+ payment is pending here

  12. melvin-bot commented on Mar 7, 2024

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  13. robertjchen commented on Mar 8, 2024

    @robertjchen
    ContributorAuthor

    cc: @twisterdotcom for assistance on #36977 (comment) Thanks! 🙏

  14. twisterdotcom commented on Mar 8, 2024

    @twisterdotcom
    Contributor

    Payment Summary:

    @situchan paid $500 here (C+)

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.DailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions