Skip to content

[$500] Tag - Extra padding above Recent section in Tag list #35423

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!


Version Number: v1.4.33-4
Reproducible in staging?: y
Reproducible in production?: n
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: Applause- Internal Team
Slack conversation:

Action Performed:

Precondition:

  • User is an employee of Collect workspace.
  • The Collect workspace has categories and tags, each has more than 8 items in the list.
  • There are recent list in Category and Tag.
  1. Go to workspace chat.
  2. Open manual request page.
  3. Enter amount > Next > Show more.
  4. Open Category and Tag list.

Expected Result:

In Tag list, there will be no extra padding above Recent, just like the Category list.

Actual Result:

There is extra padding above Recent in Tag list.

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

Bug6361193_1706637788623.20240130_234328.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~019c2250ecc51e6cc7
  • Upwork Job ID: 1752408936209432576
  • Last Price Increase: 2024-01-30

Activity

  1. github-actions commented on Jan 30, 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.
  2. melvin-bot commented on Jan 30, 2024

    @melvin-bot

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

  3. kbecciv commented on Jan 30, 2024

    @kbecciv
    Author

    We think that this bug might be related to #wave6-collect-submitters
    CC @greg-schroeder

  4. francoisl commented on Jan 30, 2024

    @francoisl
    Contributor

    Here's production (left) vs. staging (right) side by side, it's a pretty minor gap so I'm thinking we can fix it later.

    image image

  5. francoisl commented on Jan 30, 2024

    @francoisl
    Contributor

    Yeah I'll remove the blocker label for now and open this to contribution ideas to fix. Thanks!

  6. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jan 30, 2024
  7. changed the title [-]Tag - Extra padding above Recent section in Tag list[/-] [+][$500] Tag - Extra padding above Recent section in Tag list[/+] on Jan 30, 2024
  8. 7 remaining items

  9. FitseTLT commented on Jan 30, 2024

    @FitseTLT
    Contributor

    @aimane-chnaif Found the offending pr. Updated proposal

  10. FitseTLT commented on Jan 31, 2024

    @FitseTLT
    Contributor

    @francoisl @danieldoglas @DylanDylann The root cause is found and we can fix it ASAP. WDYT

  11. DylanDylann commented on Jan 31, 2024

    @DylanDylann
    Contributor

    @FitseTLT's proposal looks good to me
    🎀 👀 🎀 C+ reviewed

  12. melvin-bot commented on Jan 31, 2024

    @melvin-bot

    Current assignee @danieldoglas is eligible for the choreEngineerContributorManagement assigner, not assigning anyone new.

  13. danieldoglas commented on Jan 31, 2024

    @danieldoglas
    Contributor

    Wait, if this was caused by a recent PR (less than 7 days of the regression period), the original author of that PR needs to fix it.

  14. danieldoglas commented on Jan 31, 2024

    @danieldoglas
    Contributor

    cc @kubabutkiewicz can you please take a look into this, since it's still part of the regression period?

  15. DylanDylann commented on Jan 31, 2024

    @DylanDylann
    Contributor

    @danieldoglas Thanks for pointing out that. I will note that for next issues

  16. situchan commented on Jan 31, 2024

    @situchan
    Contributor

    I tagged original author/reviewer already in #24921 (comment)

  17. kubabutkiewicz commented on Feb 1, 2024

    @kubabutkiewicz
    Contributor

    Will create PR shortly

  18. added
    ReviewingHas a PR in review
    and removed on Feb 1, 2024
  19. kubabutkiewicz commented on Feb 1, 2024

    @kubabutkiewicz
    Contributor

    PR ready: #35541

  20. DylanDylann commented on Feb 20, 2024

    @DylanDylann
    Contributor

    @danieldoglas The author of the offending PR fixed this issue. Let's close this one

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

Metadata

Metadata

Labels

EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions