Skip to content

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

Closed

Description

@lanitochka17

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

Bug6272816_1699731986790!screenshot_2023-11-11-09-13-42-833_com android chrome

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 OwnerCurrent Issue Owner: @robertjchen

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 12, 2023
  2. melvin-bot commented on Nov 12, 2023

    @melvin-bot

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

  3. melvin-bot commented on Nov 12, 2023

    @melvin-bot
  4. OSBotify commented on Nov 12, 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. melvin-bot commented on Nov 12, 2023

    @melvin-bot

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

  6. robertjchen commented on Nov 13, 2023

    @robertjchen
    Contributor

    It sounds like the correct behavior here should be that the billable option should already be properly set upon initial entry to this page 🤔

  7. robertjchen commented on Nov 13, 2023

    @robertjchen
    Contributor

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

  8. 27 remaining items

  9. robertjchen commented on Dec 3, 2023

    @robertjchen
    Contributor

    Hoping to get to this soon

  10. melvin-bot commented on Dec 3, 2023

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

  11. melvin-bot commented on Dec 10, 2023

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

  12. robertjchen commented on Dec 13, 2023

    @robertjchen
    Contributor

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

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 staff

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions