Repository navigation
[HOLD for payment 2024-02-20] [$500] LHN - User navigated on the workspace overview page when created workspace #35755
Description
Activity
👋 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.
- Find someone who can quickly fix the issue.
- Fix the issue yourself.
Triggered auto assignment to @johnmlee101 (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.- added and removed
on Feb 5, 2024 - moved this to Release 1: Ideal Nav & Collect Simplfied Profile, Members, Categories, Workflows (approvals) in [#whatsnext] Wave 08 - Collect Plan Admins
on Feb 5, 2024 We got couple of these iPad specific bugs cc @adamgrzybowski
12 remaining items
- changed the title
[-][$500] LHN - User navigated on the workspace overview page when created workspace[/-][+][HOLD for payment 2024-02-20] [$500] LHN - User navigated on the workspace overview page when created workspace[/+]on Feb 13, 2024 Reviewinglabel has been removed, please complete the "BugZero Checklist".The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.40-5 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 2024-02-20. 🎊
For reference, here are some details about the assignees on this issue:
- @DylanDylann requires payment (Needs manual offer from BZ)
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
- [@DylanDylann] The PR that introduced the bug has been identified. Link to the PR:
- [@DylanDylann] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
- [@DylanDylann] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
- [@DylanDylann] Determine if we should create a regression test for this bug.
- [@DylanDylann] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
- [@strepanier03] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Payment Summary
- ROLE: @DylanDylann paid $(AMOUNT) via Upwork (LINK)
BugZero Checklist (@strepanier03)
- I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
- I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1754492566143000576/hired)
- I have paid out the Upwork contracts or cancelled the ones that are incorrect
- I have verified the payment summary above is correct
This issue is fixed by another PR. Could you help to confirm this issue is resolved then we can close this one
- moved this from Release 1: Ideal Nav & Collect Simplfied Profile, Members, Categories, Workflows (approvals) to Done in [#whatsnext] Wave 08 - Collect Plan Admins
on Feb 20, 2024
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: 1.4.36-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4281765&group_by=cases:section_id&group_id=306202&group_order=asc
Email or phone of affected tester (no customers): applausetester+omm1@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Precondition: user should be Signed In
Expected Result:
User should be navigated on workspace settings page
Actual Result:
User navigated on the workspace overview page
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6365935_1706965784128.RPReplay_Final1706940937.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit