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
IOU-In employee WS, the billable option in manual expense is auto moving #31240
Version Number: 1.3.98-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: 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:
Action Performed:
1.In old dot admin account, set re-bill expenses to client as "default to billable"
2. Launch app as employe login
3. Tap fab-- request money
4. Enter amount and tap next
5. Select employee WS
6. Tap show more and wait for a second and note billable option auto moving
Expected Result:
In employee workspace, the Billable option in manual expense must not auto move
Actual Result:
In employee workspace, the Billable option in manual expense is auto moving
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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.
Doesn't seem like a DeployBlocker per se. Removing the label for now- we need to figure out if it's a backend issue or if it's a frontend behavior issue (suspecting the latter).
@robertjchen@sophiepintoraetz this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!
@robertjchen@sophiepintoraetz this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!
Activity
melvin-bot commentedon Nov 12, 2023
Triggered auto assignment to @sophiepintoraetz (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Nov 12, 2023
OSBotify commentedon Nov 12, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Nov 12, 2023
Triggered auto assignment to @robertjchen (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.robertjchen commentedon Nov 13, 2023
It sounds like the correct behavior here should be that the billable option should already be properly set upon initial entry to this page 🤔
robertjchen commentedon Nov 13, 2023
Doesn't seem like a
DeployBlockerper se. Removing the label for now- we need to figure out if it's a backend issue or if it's a frontend behavior issue (suspecting the latter).27 remaining items
robertjchen commentedon Dec 3, 2023
Hoping to get to this soon
melvin-bot commentedon Dec 3, 2023
@robertjchen @sophiepintoraetz this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!
melvin-bot commentedon Dec 10, 2023
@robertjchen @sophiepintoraetz this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!
robertjchen commentedon Dec 13, 2023
Given that this is purely in the backend, let's re-create this as an internal issue and go from there.