IOU-In employee WS, the billable option in manual expense is auto moving

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

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?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6272816_1699731986770.billable.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01b1dd6ea56238a2de
• Upwork Job ID: 1729851295336857600
• Last Price Increase: 2023-11-29

Issue Owner

Current Issue Owner: @robertjchen

[melvin-bot]

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

[OSBotify]

👋 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.

[melvin-bot]

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

[robertjchen]

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]

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).

[sophiepintoraetz]

Adding the Help Wanted label as they might be able to help figure out front/back end!

[sophiepintoraetz]

@robertjchen - would you maybe be able to confirm here?

[melvin-bot]

@robertjchen, @sophiepintoraetz Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@robertjchen @sophiepintoraetz this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[sophiepintoraetz]

Waiting on @robertjchen to confirm here.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01b1dd6ea56238a2de

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @akinwale (Internal)

[robertjchen]

Marking as Internal for now for additional investigation.

[robertjchen]

Hoping to get to this soon

[melvin-bot]

@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]

@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]

Given that this is purely in the backend, let's re-create this as an internal issue and go from there.