Skip to content

The background color for the statement doesn’t match the app #33978

Closed

Description

@m-natarajan

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:
Reproducible in staging?: needs reproduction (don't have statement access)
Reproducible in production?: needs reproduction (don't have statement access)
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
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1704219570242489

Action Performed:

  1. Click on the statement link from concierge chat
  2. Observe the background color

Expected Result:

The background color should match the app

Actual Result:

the header and body have different background colors

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

Add any screenshot/video evidence

image (9)

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0148c084d01887606e
  • Upwork Job ID: 1744409181225820160
  • Last Price Increase: 2024-01-08

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 4, 2024
  2. melvin-bot commented on Jan 4, 2024

    @melvin-bot

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

  3. melvin-bot commented on Jan 4, 2024

    @melvin-bot

    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. MitchExpensify commented on Jan 8, 2024

    @MitchExpensify
    Contributor

    Reproduced!

  5. MitchExpensify commented on Jan 8, 2024

    @MitchExpensify
    Contributor
  6. added
    InternalRequires API changes or must be handled by Expensify staff
    on Jan 8, 2024
  7. melvin-bot commented on Jan 8, 2024

    @melvin-bot
  8. melvin-bot commented on Jan 8, 2024

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @sobitneupane (Internal)

  9. 21 remaining items

  10. rlinoz commented on Jan 19, 2024

    @rlinoz
    Contributor

    I forgot to add $ to the PR fixing this issue, and I am not sure how to trigger the payment automation for the C+ review.

    Can you help us here @MitchExpensify, please?

  11. MitchExpensify commented on Jan 19, 2024

    @MitchExpensify
    Contributor

    Payment summary:

    Please make the request in NewDot for compensation on Jan 24th, @sobitneupane - Thank you!

  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Jan 24, 2024
  13. melvin-bot commented on Feb 1, 2024

    @melvin-bot

    @rlinoz @sobitneupane @MitchExpensify @dubielzyk-expensify this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!

  14. rlinoz commented on Feb 1, 2024

    @rlinoz
    Contributor

    I think we are just missing @sobitneupane make the request in NewDot?

  15. MitchExpensify commented on Feb 3, 2024

    @MitchExpensify
    Contributor

    Yes and this can be closed while we wait on that

  16. JmillsExpensify commented on Feb 14, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @sobitneupane based on this summary.

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.DailyKSv2DesignEngineeringInternalRequires API changes or must be handled by Expensify staffNeeds ReproductionReproducible steps needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions