mWeb-Tag-When dependent tags are being disabled, "tag no longer valid" message is not shown

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.4 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4694802 Issue reported by: Applause - Internal Team

Action Performed:

1. Go to https://staging.new.expensify.com/hom
2. Login as employee
3. Open Workspace chat
4. Create an expense selecting category and dependent tags
5. Now in other device open admin account
6. Disable the category and all dependent tags option
7. Now as employee, open the expense

Expected Result:

When dependent tags are being disabled, "tag no longer valid" message must be shown

Actual Result:

For category after disabled "category no longer valid" message shown but for dependent tags no message displayed

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• [ ] Android: Native
• [x] Android: mWeb Chrome
• [ ] iOS: Native
• [ ] iOS: mWeb Safari
• [ ] MacOS: Chrome / Safari
• [ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/83b5deca-ffb8-48de-b6a5-6f5705dcf6b6

https://github.com/Expensify/App/assets/78819774/84e97238-14f0-4a6d-b227-2e7f7a74f711

View all open jobs on GitHub

[melvin-bot[bot]]

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.

[lanitochka17]

@twisterdotcom FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[nyomanjyotisa]

Require BE fix There are no violations on the API response for multilevel tags & dependant tags if it is disabled

[melvin-bot[bot]]

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

[melvin-bot[bot]]

@twisterdotcom Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot[bot]]

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

[twisterdotcom]

Okay, making Internal

[melvin-bot[bot]]

@twisterdotcom this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[twisterdotcom]

No volunteers yet. Not really a hot pick for now.

[twisterdotcom]

Asking for some help in wave-control: https://expensify.slack.com/archives/C06ML6X0W9L/p1722599730089979

[twisterdotcom]

Going to try to consolidate my dependent tag issues and find a single assignee

[yuwenmemon]

Will look at this as a part of the tags project soon.

[twisterdotcom]

Same as above.

[yuwenmemon]

I think this actually might just be solved with the violations project, right @twisterdotcom?

[twisterdotcom]

Possible. Do we have a PR to link to?

[yuwenmemon]

No I was just thinking about it in the abstract 😂

The violations project isn't complete yet either. But a man can dream...

[twisterdotcom]

Shall we just close this?

[yuwenmemon]

Yeah