Skip to content

[HOLD for payment 2024-06-28] [$125] [Search v1] No background color placeholder exists for receipt thumbnail #43393

Description

@luacmartins

Coming from this thread, the receipt thumbnail doesn't have a placeholder background color.

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019803a773929eed48
  • Upwork Job ID: 1800191951832943611
  • Last Price Increase: 2024-06-10
  • Automatic offers:
    • dukenv0307 | Reviewer | 102688635
    • Krishna2323 | Contributor | 102688638
Issue OwnerCurrent Issue Owner: @trjExpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 10, 2024
  2. self-assigned this
    on Jun 10, 2024
  3. melvin-bot commented on Jun 10, 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. shawnborton commented on Jun 10, 2024

    @shawnborton
    Contributor

    The color should be the same that we use for the empty state thumbnail:
    CleanShot 2024-06-10 at 17 41 16@2x

    Which probably means we need to consider the hover state too - I think we bump that background color a shade up when the expense or report row is hovered.

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jun 10, 2024
  6. melvin-bot commented on Jun 10, 2024

    @melvin-bot
  7. changed the title [-][Search v1] No background color placeholder exists for receipt thumbnail[/-] [+][$250] [Search v1] No background color placeholder exists for receipt thumbnail[/+] on Jun 10, 2024
  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 10, 2024
  9. melvin-bot commented on Jun 10, 2024

    @melvin-bot

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

  10. changed the title [-][$250] [Search v1] No background color placeholder exists for receipt thumbnail[/-] [+][$125] [Search v1] No background color placeholder exists for receipt thumbnail[/+] on Jun 10, 2024
  11. 20 remaining items

  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jun 21, 2024
  13. changed the title [-][$125] [Search v1] No background color placeholder exists for receipt thumbnail[/-] [+][HOLD for payment 2024-06-28] [$125] [Search v1] No background color placeholder exists for receipt thumbnail[/+] on Jun 21, 2024
  14. melvin-bot commented on Jun 21, 2024

    @melvin-bot

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

  15. melvin-bot commented on Jun 21, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.85-7 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-06-28. 🎊

    For reference, here are some details about the assignees on this issue:

  16. melvin-bot commented on Jun 21, 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:

    • [@dukenv0307] The PR that introduced the bug has been identified. Link to the PR:
    • [@dukenv0307] 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:
    • [@dukenv0307] 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:
    • [@dukenv0307] Determine if we should create a regression test for this bug.
    • [@dukenv0307] 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.
    • [@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  17. trjExpensify commented on Jun 28, 2024

    @trjExpensify
    Contributor

    I don't think we need a regression test for this, and it was a cheeky bug in a new feature release.

    Payment summary as follows:

    Paid both, closing!

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

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions