You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-04-25] [$250] Workspace - "Select multiple" in Members and Categories page has different style #59498
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:
Launch the app.
Go to workspace settings > Members.
Invite another member if there is no other member.
Long tap on the member > Select.
Go to workspace settings > Categories.
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.
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
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:
@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]
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.
[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:
Go to workspace settings > Members.
Invite another member if there is no other member.
Long tap on the member > Select.
Go to workspace settings > Categories.
Long tap on any category > Select.
Verify "Select multiple" in Members and Categories page will have the same style.
Activity
melvin-bot commentedon Apr 1, 2025
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.NicMendonca commentedon Apr 2, 2025
@Expensify/design fyi!
[-]Workspace - "Select multiple" in Members and Categories page has different style[/-][+][$250] Workspace - "Select multiple" in Members and Categories page has different style[/+]melvin-bot commentedon Apr 2, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021907506240427805442
melvin-bot commentedon Apr 2, 2025
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (
External)dannymcclain commentedon Apr 2, 2025
😮
The categories example is the correct one 👍
dubielzyk-expensify commentedon Apr 3, 2025
So weird how these bugs happen, but good we caught it. What Danny said looks right
shawnborton commentedon Apr 3, 2025
Agree, and agree!
18 remaining items
melvin-bot commentedon Apr 18, 2025
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:
melvin-bot commentedon Apr 18, 2025
@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]
NicMendonca commentedon Apr 25, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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 👎
NicMendonca commentedon Apr 25, 2025
@Themoonalsofall sent you the offer!
NicMendonca commentedon Apr 28, 2025
@Themoonalsofall ty, paid!
sobitneupane commentedon Apr 28, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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:
Do we agree 👍 or 👎
NicMendonca commentedon Apr 28, 2025
Payment summary
C+: @sobitneupane -- $250 paid via NewDot
C: @Themoonalsofall -- $250 paid via Upwork (done!)
garrettmknight commentedon May 20, 2025
$250 approved for @sobitneupane