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

Workspace - Does not detect the expense category after turning on and off in the policy #44377

Closed
1 of 6 tasks
izarutskaya opened this issue Jun 25, 2024 · 8 comments
Closed
1 of 6 tasks
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2

Comments

@izarutskaya
Copy link

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.0.8
Reproducible in staging?: Y
Reproducible in production?: Y
Found when validating PR : #43869
Email or phone of affected tester (no customers): applausetester+az090524@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Prerequsites:

  1. A workspace created
  2. Expenses submited in the workspace

Steps:

  1. Open the new Search page
  2. Verify the information of the expenses in the workspace
  3. Open the workspace
  4. Enable Taxes and Tags options
  5. Verify that the information of the expenses are correct
  6. Go back to the workspace
  7. Disable Categories, Taxes and Tags options
  8. Go back to the information of the expense and verify that is an error message in the "Category"
  9. Go to the workspace, enable "Categories"
  10. Tap on the Categories, select all the categories and with the menu in the header Enable all
  11. Go back to the expense in the new Search page

Expected Result:

The error of the Category should not longer be presented

Actual Result:

The error is still present even though the categories are already active

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

Bug6523195_1719247492052.Video_de_WhatsApp_2024-06-24_a_las_11.21.11_222a31f2.mp4
Bug6523195_1719247492066.prod.mp4

View all open jobs on GitHub

@izarutskaya izarutskaya added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Jun 25, 2024
Copy link

melvin-bot bot commented Jun 25, 2024

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

@izarutskaya
Copy link
Author

We think this issue might be related to the #collect project.

@melvin-bot melvin-bot bot added the Overdue label Jun 27, 2024
Copy link

melvin-bot bot commented Jun 28, 2024

@adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!

Copy link

melvin-bot bot commented Jul 2, 2024

@adelekennedy 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

Copy link

melvin-bot bot commented Jul 4, 2024

@adelekennedy Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

Copy link

melvin-bot bot commented Jul 8, 2024

@adelekennedy 12 days overdue now... This issue's end is nigh!

@adelekennedy
Copy link

I somehow missed this one 😮‍💨

@melvin-bot melvin-bot bot removed the Overdue label Jul 8, 2024
@adelekennedy
Copy link

i can't reproduce this one - and we're on such a later version that I think we're safe to close for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2
Projects
None yet
Development

No branches or pull requests

2 participants