Categories & Tags - Not here page opens from GL code row

[lanitochka17]

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.7-3
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Issue found when executing PR #43149

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Collect workspace settings > Categories
3. Click on any category
4. Click GL code

Expected Result:

GL code editor will open

Actual Result:

Not here page opens.
The same issue also happens with tags

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

Add any screenshot/video evidence

Bug6543217_1721078508096.GL.mp4

View all open jobs on GitHub

[melvin-bot]

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

[github-actions]

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

[lanitochka17]

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

[rushatgabhane]

@lanitochka17 is that a collect workspace?

[marcaaron]

@rushatgabhane any ideas on this one?

[marcaaron]

My first guess would be it's related to #43149 gonna assign @Gonals since they are leading this up and QA has just started to run regressions.

[rushatgabhane]

@marcaaron yes this is happening because the user is allowed to visit the page only if it is a collect workspace

[rushatgabhane]

Not a blocker in my opinion. It will be replaced by Upgrade flow by @allroundexperts

[Gonals]

Yep, not. blocker and not a bug. This is currently expected in non-control