Skip to content

[Waiting on Checklist - HOLD for payment 2024-11-05] [$250] QBO - Connection options are missing in QBO connection #46445

New issue
New issue
Closed
Closed
[Waiting on Checklist - HOLD for payment 2024-11-05] [$250] QBO - Connection options are missing in QBO connection#46445
Assignees
tgolenyuwenmemontwisterdotcomhungvu193ishpaul777
Labels
Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Description

@lanitochka17
lanitochka17
opened on Jul 29, 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: 9.0.14-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team

Action Performed:

  1. Log in to the app with a new expensifail account
  2. Create a new workspace
  3. Go to more features > enable accounting
  4. Navigate to the accountings page and connect with QBO
  5. When you are navigated to the QBO page enter the credentials and finish the connection
  6. After connecting with QBO, you will be navigated to the app
  7. Wait for the connection to sync

Expected Result:

QBO options (Import, Export, Card reconciliation and Advanced options) are displayed

Actual Result:

QBO options (Import, Export, Card reconciliation, and Advanced options) are not displayed

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

Bug6556582_1722281658856.2024-07-29_22_24_02.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @ishpaul777
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021841525897082466980
  • Upwork Job ID: 1841525897082466980
  • Last Price Increase: 2024-10-09
  • Automatic offers:
    • ishpaul777 | Reviewer | 104412598

Activity

  1. lanitochka17
    added
    DailyKSv2
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 29, 2024
  2. melvin-bot
    assigned
    twisterdotcom
    on Jul 29, 2024

  3. melvin-bot commented on Jul 29, 2024

    @melvin-bot
    melvin-botBot
    on Jul 29, 2024 – with Melvin Bot

    Triggered auto assignment to @twisterdotcom (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.

  4. lanitochka17
    added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    and removed
    DailyKSv2
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 29, 2024
  5. melvin-bot
    assigned
    tgolen
    on Jul 29, 2024

  6. melvin-bot commented on Jul 29, 2024

    @melvin-bot
    melvin-botBot
    on Jul 29, 2024 – with Melvin Bot

    Triggered auto assignment to @tgolen (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  7. github-actions
    added
    Engineering
    HourlyKSv2
    on Jul 29, 2024

  8. github-actions commented on Jul 29, 2024

    @github-actions
    github-actionsBot
    on Jul 29, 2024 – with GitHub Actions
    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.

  9. lanitochka17 commented on Jul 29, 2024

    @lanitochka17
    lanitochka17
    on Jul 29, 2024
    Author

    We think that this bug might be related to #wave-collect - Release 1

  10. tgolen commented on Jul 29, 2024

    @tgolen
    tgolen
    on Jul 29, 2024
    Contributor

    @kosmydel @hungvu193 @arosiclair Is it possible this is related to #44733 ?

  11. 103 remaining items

  12. melvin-bot commented on Oct 29, 2024

    @melvin-bot
    melvin-botBot
    on Oct 29, 2024 – with Melvin Bot

    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:

    • [@hungvu193 / @ishpaul777] The PR that introduced the bug has been identified. Link to the PR:
    • [@hungvu193 / @ishpaul777] 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:
    • [@hungvu193 / @ishpaul777] 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:
    • [@hungvu193 / @ishpaul777] Determine if we should create a regression test for this bug.
    • [@hungvu193 / @ishpaul777] 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.
    • [@twisterdotcom] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
  13. melvin-bot
    added
    DailyKSv2
    and removed
    WeeklyKSv2
    on Nov 4, 2024

  14. twisterdotcom commented on Nov 5, 2024

    @twisterdotcom
    twisterdotcom
    on Nov 5, 2024
    Contributor

    Payment Summary:

  15. twisterdotcom
    changed the title [-][HOLD for payment 2024-11-05] [$250] QBO - Connection options are missing in QBO connection[/-] [+][Waiting on Checklist - HOLD for payment 2024-11-05] [$250] QBO - Connection options are missing in QBO connection[/+] on Nov 5, 2024

  16. garrettmknight commented on Nov 6, 2024

    @garrettmknight
    garrettmknight
    on Nov 6, 2024
    Contributor

    @hungvu193 please complete the checklist

  17. ishpaul777 commented on Nov 6, 2024

    @ishpaul777
    ishpaul777
    on Nov 6, 2024
    Contributor

    Will fill checklist today 👍

  18. ishpaul777 commented on Nov 8, 2024

    @ishpaul777
    ishpaul777
    on Nov 8, 2024
    Contributor

    I am on it now, sorry for delay

  19. ishpaul777 commented on Nov 12, 2024

    @ishpaul777
    ishpaul777
    on Nov 12, 2024
    Contributor

    i keep on distracting with other tasks and i am on limited availability i swear am on it 🙇

    Edit: Done filled it finally 👍

  20. ishpaul777 commented on Nov 12, 2024

    @ishpaul777
    ishpaul777
    on Nov 12, 2024
    Contributor

    BugZero Checklist:

    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other: Not a bug, but a race condition side effect on how new connection with Onyx updates works.

    Where bug was reported:

    • 2a. Reported on production
    • 2b. Reported on staging (deploy blocker)
    • 2c. Reported on a PR
    • 2z. Other: Reported on staging as DB, but was also reproducable on production by folks

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:

    • [@ishpaul777] 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: No specific PR in E/App this was like this since the connection api is implemented on BE PR (i dont have access to BE repo)

    • [@ishpaul777] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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: Not critical there was only mili second difference and the options show up, It does not block any user flow

    • [@ishpaul777] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again. No need, same reason as above

  21. twisterdotcom
    closed this as completedon Nov 14, 2024

  22. garrettmknight commented on Nov 20, 2024

    @garrettmknight
    garrettmknight
    on Nov 20, 2024
    Contributor

    $250 approved for @hungvu193

  23. ishpaul777 commented on Nov 20, 2024

    @ishpaul777
    ishpaul777
    on Nov 20, 2024
    Contributor

    This is not yet paid for me on upwork @twisterdotcom

    Screenshot 2024-11-20 at 7 50 46 PM

  24. twisterdotcom commented on Nov 20, 2024

    @twisterdotcom
    twisterdotcom
    on Nov 20, 2024
    Contributor

    Weird, that didn't show up in Upwork for me at all. All done now.

  25. trjExpensify
    moved this from Release 2.5: SuiteWorld (Sept 9th) to Done in [#whatsnext] #wave-collecton Jul 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions