Skip to content

Create expense - "Just track it (Don't submit it)" row is still shown in Create expense flow #54953

Closed

Description

@izarutskaya

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: v9.0.82-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: #53760
Email or phone of affected tester (no customers): emilio.utest+2382fff38@gmail.com
Issue reported by: Applause Internal Team
Device used: Macbook Pro 2023 / Sonoma 14.4.1
App Component: Chat Report View

Action Performed:

  1. Open the New expensify app
  2. Log into the app
  3. Click on the + button
  4. Select the Create expense option
  5. Choose the Manual expense
  6. Provide an expense value
  7. Navigate to the next step
  8. Make sure the Just track it (don't submit it) option row is not visible

Expected Result:

User expects not to see Just track it (Don't submit it) option

Actual Result:

Just track it (Don't submit it) option is shown

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6708738_1736309224876.PR_53760_Desktop.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 8, 2025
  2. melvin-bot commented on Jan 8, 2025

    @melvin-bot

    Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. trjExpensify commented on Jan 8, 2025

    @trjExpensify
    Contributor

    @grgia @JKobrynski isn't this because we reverted the PR?

  4. melvin-bot commented on Jan 14, 2025

    @melvin-bot

    @abekkala Eep! 4 days overdue now. Issues have feelings too...

  5. abekkala commented on Jan 14, 2025

    @abekkala
    Contributor
  6. melvin-bot commented on Jan 20, 2025

    @melvin-bot

    @abekkala Huh... This is 4 days overdue. Who can take care of this?

  7. abekkala commented on Jan 21, 2025

    @abekkala
    Contributor

    checking with @grgia

  8. grgia commented on Jan 21, 2025

    @grgia
    Contributor

    I'm pretty sure this was fixed. We can retest after #55016 hits staging

    cc @JKobrynski

  9. self-assigned this
    on Jan 21, 2025
  10. melvin-bot commented on Jan 22, 2025

    @melvin-bot

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

  11. abekkala commented on Jan 23, 2025

    @abekkala
    Contributor

    note: not merged to staging yet.
    keeping an eye then we can retest

  12. grgia commented on Jan 24, 2025

    @grgia
    Contributor

    Closing out, this isnt a bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions