Skip to content

[Due for payment 2025-09-17] Workspace - Expense policy section is not grayed out when workspace is created offline #70036

Closed

Description

@jponikarchuk

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.2.2-0
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 TestRail: #66143
Email or phone of affected tester (no customers): applausetester+030904kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • Log in with Expensifail account.
  1. Go to staging.new.expensify.com
  2. Go offline.
  3. Create a workspace.
  4. Go to workspace settings > Overview.
  5. Scroll down to Expense policy.

Expected Result:

Expense policy section will be grayed out when workspace is created offline.

Actual Result:

Expense policy section is not grayed out when workspace is created offline.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @lydiabarclay

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 7, 2025
  2. melvin-bot commented on Sep 7, 2025

    @melvin-bot

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

  3. melvin-bot commented on Sep 7, 2025

    @melvin-bot

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

  4. melvin-bot commented on Sep 7, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 7, 2025

    @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 Sep 8, 2025
  7. iwiznia commented on Sep 8, 2025

    @iwiznia
    Contributor

    Removing deploy blocker as this is only missing the offline behavior plus it is only under beta

  8. 1 remaining item

  9. added and removed on Sep 10, 2025
  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Sep 10, 2025
  11. changed the title [-]Workspace - Expense policy section is not grayed out when workspace is created offline[/-] [+][Due for payment 2025-09-17] Workspace - Expense policy section is not grayed out when workspace is created offline[/+] on Sep 10, 2025
  12. melvin-bot commented on Sep 10, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  13. melvin-bot commented on Sep 10, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.8-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-09-17. 🎊

  14. melvin-bot commented on Sep 10, 2025

    @melvin-bot

    @mollfpr @lydiabarclay The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  15. lydiabarclay commented on Sep 11, 2025

    @lydiabarclay
    Contributor

    @mollfpr no payment actually needed after the regression period, right?

  16. lydiabarclay commented on Sep 17, 2025

    @lydiabarclay
    Contributor

    @mollfpr no regressions or C+ assigned to this, so I'm closing. Feel free to reopen if needed!

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions