Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HOLD for payment 2024-09-16] Categories - Unable to select subcategory as the default spend category #48690

Closed
6 tasks done
IuliiaHerets opened this issue Sep 6, 2024 · 17 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Weekly KSv2

Comments

@IuliiaHerets
Copy link

IuliiaHerets commented Sep 6, 2024

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.0.30-7
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+kh010901@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Categories.
  3. Add a category in X: Y format.
  4. Click Settings.
  5. Click on any spend category.
  6. Select the subcategory (Y).

Expected Result:

Subcategory can be selected as the default spend category.

Actual Result:

Subcategory cannot be selected as the default spend category. It reverts to the previous category after selecting the subcategory.

RBR is shown next to the workspace but there is no error message after selecting the subcategory as the default category.

Workaround:

Unknown

Platforms:

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6595057_1725606854193.20240906_151151.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @twisterdotcom
@IuliiaHerets IuliiaHerets added DeployBlockerCash This issue or pull request should block deployment Bug Something is broken. Auto assigns a BugZero manager. labels Sep 6, 2024
Copy link

melvin-bot bot commented Sep 6, 2024

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

Copy link

melvin-bot bot commented Sep 6, 2024

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

@melvin-bot melvin-bot bot added the Daily KSv2 label Sep 6, 2024
@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Sep 6, 2024
Copy link
Contributor

github-actions bot commented Sep 6, 2024

👋 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.

@twisterdotcom
Copy link
Contributor

twisterdotcom commented Sep 6, 2024

Don't need another recording to show this one. Very obvious.

8bede96a787452b4-LHR

previous exception InvalidArgumentException - fab9bc9a701be21ffce3c1fe9262a5ba ~~ exceptionMessage: 'MCC group category need to be on the policy' exceptionFile: '/git/releases/expensify.com/95742ca/lib/PolicyAPI.php' exceptionLine: '6092' exceptionCode: '402'

@lakchote is this an easy fix? Can we make it external?

@twisterdotcom
Copy link
Contributor

I can't find an offending PR here tbh.

@lakchote
Copy link
Contributor

lakchote commented Sep 6, 2024

The offending PR is #48391 (cc @BartoszGrajdek @marcaaron)

It adds the category spend selector, without it Settings are empty which means the offending code is in the PR:

image

@lakchote
Copy link
Contributor

lakchote commented Sep 6, 2024

CP requested here

@lakchote
Copy link
Contributor

lakchote commented Sep 6, 2024

QA tests passed since CP (link).

Removing the deploy blocker label.

@lakchote lakchote removed the DeployBlockerCash This issue or pull request should block deployment label Sep 6, 2024
Copy link

melvin-bot bot commented Sep 6, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@twisterdotcom
Copy link
Contributor

Can we close this now @lakchote?

@lakchote
Copy link
Contributor

Can we close this now @lakchote?

Yes, closing!

@ishpaul777
Copy link
Contributor

Hey can we please reopen to process payment here for #48708, cc @lakchote @twisterdotcom

@twisterdotcom
Copy link
Contributor

twisterdotcom commented Sep 12, 2024

Ah, okay. When did it hit prod?

@twisterdotcom twisterdotcom reopened this Sep 12, 2024
@ishpaul777
Copy link
Contributor

ishpaul777 commented Sep 16, 2024

Deployed 9 sept. with this checklist #48664, should be ready for payment

@twisterdotcom twisterdotcom added Awaiting Payment Auto-added when associated PR is deployed to production and removed Reviewing Has a PR in review labels Sep 16, 2024
@twisterdotcom twisterdotcom changed the title Categories - Unable to select subcategory as the default spend category [HOLD for payment 2024-09-16] Categories - Unable to select subcategory as the default spend category Sep 16, 2024
@twisterdotcom
Copy link
Contributor

Payment Summary:

@ishpaul777
Copy link
Contributor

Accepted Thanks!

@ishpaul777
Copy link
Contributor

@twisterdotcom Could you please release payment https://www.upwork.com/nx/wm/workroom/38389275/overview

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Weekly KSv2
Projects
None yet
Development

No branches or pull requests

4 participants