Skip to content

[Due for payment 2026-10-01] Not here page opens when people admin opens workspace settings after downgrading to Collect #95223

Closed

Description

@applause-bot

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.4.26-5
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #92875
Email or phone of affected tester (no customers): sdjonisjdodjnosjio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • Create a Control workspace.
  • Invite member as people admin.
  1. Go to staging.new.expensify.com
  2. [Owner] Go to workspace settings > Overview.
  3. [Owner] Click Plan type > Collect > Save > Downgrade workspace.
  4. [People admin] Open the workspace settings.

Expected Result:

People admin can still see Overview and Members after owner downgrades workspace to Collect.

Actual Result:

Not here page opens when people admin opens workspace settings after owner downgrades workspace to Collect.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7197737_1783008810466.10.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Svetlana Lazutkina
Bug ID: 7197737

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. applause-bot commented on Jul 2, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/40f2f6fb798afd6ef6d7b257cc925941770248059bda244caa3589277d2c62fb

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 2, 2026
  3. melvin-bot commented on Jul 2, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #92875

  4. melvin-bot commented on Jul 2, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Jul 2, 2026

    @github-actions
    Contributor

    👋 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.
  6. removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jul 2, 2026
  7. flodnv commented on Jul 2, 2026

    @flodnv
    Contributor

    Not severe enough to block the deploy, @ShridharGoel will check soon

  8. added and removed on Jul 2, 2026
  9. 50 remaining items

  10. changed the title [-]Not here page opens when people admin opens workspace settings after downgrading to Collect[/-] [+][Due for payment 2026-10-01] Not here page opens when people admin opens workspace settings after downgrading to Collect[/+] on Oct 1, 2026
  11. melvin-bot commented on Oct 1, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  12. melvin-bot commented on Oct 1, 2026

    @melvin-bot

    Payment Summary

    • Contributor: @ShridharGoel does not require payment (Contractor)
    • Assignee: @dmkt9 requires payment (Needs manual offer from BZ)

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  13. mallenexpensify commented on Oct 3, 2026

    @mallenexpensify
    Contributor

    @dmkt9 are you due payment here? If so, how much? Please link to the PR you reviewed. Thx

  14. dmkt9 commented on Oct 5, 2026

    @dmkt9
    Contributor

    @dmkt9 are you due payment here? If so, how much? Please link to the PR you reviewed. Thx

    @mallenexpensify I've reviewed this PR: #99245 (comment). I believe the payment due is $250

  15. mallenexpensify commented on Oct 6, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @dmkt9 paid $250 via Upwork

    @dmkt9 paid, can you please accept the job below? Please reply here and tag me once you have.
    https://www.upwork.com/jobs/~022107262481628299712

  16. dmkt9 commented on Oct 6, 2026

    @dmkt9
    Contributor

    Contributor+: @dmkt9 due $250 via Upwork

    @mallenexpensify Thanks. I've accepted the offer

  17. ShridharGoel commented on Oct 6, 2026

    @ShridharGoel
    Contributor

    Can we close this?

  18. mallenexpensify commented on Oct 6, 2026

    @mallenexpensify
    Contributor

    @dmkt9 paid, summary updated above. Thx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions