Skip to content

[Due for payment 2025-04-25] [$250] Workspace - "Select multiple" in Members and Categories page has different style #59498

Closed

Description

@vincdargento

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: 9.1.22-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+sdsoidsj@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: iPhone 15 Pro Max / iOS 18.3
App Component: Workspace Settings

Action Performed:

  1. Launch the app.
  2. Go to workspace settings > Members.
  3. Invite another member if there is no other member.
  4. Long tap on the member > Select.
  5. Go to workspace settings > Categories.
  6. Long tap on any category > Select.

Expected Result:

"Select multiple" in Members and Categories page will have the same style.

Actual Result:

"Select multiple" in Members and Categories page has different style.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021907506240427805442
  • Upwork Job ID: 1907506240427805442
  • Last Price Increase: 2025-04-02
Issue OwnerCurrent Issue Owner: @sobitneupane

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 1, 2025
  2. melvin-bot commented on Apr 1, 2025

    @melvin-bot

    Triggered auto assignment to @NicMendonca (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.

  3. NicMendonca commented on Apr 2, 2025

    @NicMendonca
    Contributor

    @Expensify/design fyi!

  4. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Apr 2, 2025
  5. changed the title [-]Workspace - "Select multiple" in Members and Categories page has different style[/-] [+][$250] Workspace - "Select multiple" in Members and Categories page has different style[/+] on Apr 2, 2025
  6. melvin-bot commented on Apr 2, 2025

    @melvin-bot
  7. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 2, 2025
  8. melvin-bot commented on Apr 2, 2025

    @melvin-bot

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

  9. dannymcclain commented on Apr 2, 2025

    @dannymcclain
    Contributor

    😮

    The categories example is the correct one 👍

  10. dubielzyk-expensify commented on Apr 3, 2025

    @dubielzyk-expensify
    Contributor

    So weird how these bugs happen, but good we caught it. What Danny said looks right

  11. shawnborton commented on Apr 3, 2025

    @shawnborton
    Contributor

    Agree, and agree!

  12. 18 remaining items

  13. melvin-bot commented on Apr 18, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.29-10 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 2025-04-25. 🎊

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

    • @sobitneupane requires payment through NewDot Manual Requests
    • @Themoonalsofall requires payment (Needs manual offer from BZ)
  14. melvin-bot commented on Apr 18, 2025

    @melvin-bot

    @sobitneupane @NicMendonca @sobitneupane The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. NicMendonca commented on Apr 25, 2025

    @NicMendonca
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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:

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal Template
    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Precondition:

    Test:

    Do we agree 👍 or 👎

  16. NicMendonca commented on Apr 25, 2025

    @NicMendonca
    Contributor

    @Themoonalsofall sent you the offer!

  17. NicMendonca commented on Apr 28, 2025

    @NicMendonca
    Contributor

    @Themoonalsofall ty, paid!

  18. sobitneupane commented on Apr 28, 2025

    @sobitneupane
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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: [vip-travel] Create Trip Details Screen #52823 (comment)

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    1. Go to workspace settings > Members.
    2. Invite another member if there is no other member.
    3. Long tap on the member > Select.
    4. Go to workspace settings > Categories.
    5. Long tap on any category > Select.
    6. Verify "Select multiple" in Members and Categories page will have the same style.

    Do we agree 👍 or 👎

  19. NicMendonca commented on Apr 28, 2025

    @NicMendonca
    Contributor

    Payment summary

    C+: @sobitneupane -- $250 paid via NewDot
    C: @Themoonalsofall -- $250 paid via Upwork (done!)

  20. garrettmknight commented on May 20, 2025

    @garrettmknight
    Contributor

    $250 approved for @sobitneupane

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions