You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Workspace - Sensitive information is visible when deleting a workspace and creating a new #33557
Version Number: 1.4.16.3 Reproducible in staging?: Y Reproducible in production?: Unable to check the Plaid connection in prod 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 Expensify/Expensify Issue URL: Issue reported by: Applause - Internal Team Slack conversation:
👋 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:
Identify the pull request that introduced this issue and revert it.
I agree this does not seem like a blocker. Additionally its the same user who is inserting this data, the problem would be if the data is shared across sessions
Activity
melvin-bot commentedon Dec 23, 2023
Triggered auto assignment to @bfitzexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Dec 23, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)github-actions commentedon Dec 23, 2023
👋 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:
melvin-bot commentedon Dec 23, 2023
Triggered auto assignment to @robertjchen (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.shubham1206agra commentedon Dec 24, 2023
@mountiny This should be fixed with VBBA refactor (not 100% sure)
hoangzinh commentedon Dec 25, 2023
mountiny commentedon Dec 25, 2023
I agree this does not seem like a blocker. Additionally its the same user who is inserting this data, the problem would be if the data is shared across sessions