Skip to content

Created workspace is not immediately reflected in LHN #18323

Closed

Description

@kavimuru

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Click on ‘Profile’ avatar
  2. Click on ‘Workspaces’ link
  3. Click on ‘New workspace’ button
  4. Observe that workspace is displayed on LHN briefly and disappeared

Expected Result:

Created workspace should be displayed on LHN upon creation

Actual Result:

Created workspace is not displayed on LHN upon creation

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.9-4
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

2023-05-03.04.12.56.mp4
Recording.464.mp4

Expensify/Expensify Issue URL:
Issue reported by: @Natnael-Guchima
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683076759095689

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0118b0a2d7058654a7
  • Upwork Job ID: 1653811047192453120
  • Last Price Increase: 2023-05-03

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 3, 2023
  2. MelvinBot commented on May 3, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @flaviadefaria (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. MelvinBot commented on May 3, 2023

    @MelvinBot
    Contributor

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. OSBotify commented on May 3, 2023

    @OSBotify
    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.
  5. MelvinBot commented on May 3, 2023

    @MelvinBot
    Contributor

    Triggered auto assignment to @robertjchen (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  6. flaviadefaria commented on May 3, 2023

    @flaviadefaria
    Contributor

    @robertjchen I'll leave this as hourly so that you can look into it as soon as possible.

  7. marcaaron commented on May 3, 2023

    @marcaaron
    Contributor

    Hmm I think this is maybe related to some backend change. I tried to reproduce this and what I see is:

    2023-05-03_07-07-48

    If you turn off the "Use staging server" option in "Test preference" it will not be broken.

    @joelbettner should get this on your radar as you are the web deployer this week. Once we deploy Web all NewDot versions will experience this issue.

  8. 7 remaining items

  9. melvin-bot commented on May 11, 2023

    @melvin-bot

    @iwiznia, @flaviadefaria Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  10. iwiznia commented on May 11, 2023

    @iwiznia
    Contributor

    No update

  11. Natnael-Guchima commented on May 12, 2023

    @Natnael-Guchima

    Hello @iwiznia @flaviadefaria 👋. This issue seems to be fixed and deployed to production. I was testing it now, and it seems to be working fine.

    2023-05-12.10.29.38.mp4
  12. Natnael-Guchima commented on May 17, 2023

    @Natnael-Guchima

    A gentle bump @iwiznia @flaviadefaria

  13. iwiznia commented on May 17, 2023

    @iwiznia
    Contributor

    @flaviadefaria I assume @Natnael-Guchima is asking for payment for reporting the bug

  14. flaviadefaria commented on May 17, 2023

    @flaviadefaria
    Contributor

    Paying him now!

  15. flaviadefaria commented on May 17, 2023

    @flaviadefaria
    Contributor

    Offer sent, waiting for it to be accepted so that I can you @Natnael-Guchima.

  16. Natnael-Guchima commented on May 17, 2023

    @Natnael-Guchima

    Offer sent, waiting for it to be accepted so that I can you @Natnael-Guchima.

    Accepted. Thanks @flaviadefaria .

  17. flaviadefaria commented on May 17, 2023

    @flaviadefaria
    Contributor

    Paid so closing this!

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions