Skip to content

[HOLD for payment 2024-10-10] [$250] connect to Quickbooks Dekstop on OldDot, the admin room in newdot shows incomplete system messages #47830

Closed

Description

@m-natarajan

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.23-0
Reproducible in staging?: y
Reproducible in production?: y
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: @dubielzyk-expensify
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1724242725049269

Action Performed:

  1. Login with same account in OD and ND
  2. Go to workspace in OD
  3. Connect to Quickbooks Dekstop
  4. Go to # admin room of the same workspace

Expected Result:

There shouldn't be any incomplete message

Actual Result:

“removed the connection to message appears

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

IMG_0925

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021833242408324478296
  • Upwork Job ID: 1833242408324478296
  • Last Price Increase: 2024-09-23
  • Automatic offers:
    • DylanDylann | Contributor | 104119799
Issue OwnerCurrent Issue Owner: @dylanexpensify

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 22, 2024
  2. daledah commented on Aug 22, 2024

    @daledah
    Contributor

    Edited by proposal-police: This proposal was edited at 2024-08-22 02:59:49 UTC.

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    • “removed the connection to message appears

    What is the root cause of that problem?

    • We don't have a specific logic to display POLICYCHANGELOG_DELETE_INTEGRATION, so it displays the message[0].text, which is removed the connection to.

    What changes do you think we should make in order to solve the problem?

            } else if (action.actionName === CONST.REPORT.ACTIONS.TYPE.POLICY_CHANGE_LOG.DELETE_INTEGRATION) {
                children = (
                    <ReportActionItemBasicMessage
                        message={`Removed connection to ${CONST.POLICY.CONNECTIONS.NAME_USER_FRIENDLY[ReportActionsUtils.getOriginalMessage(action).connectionName]}`}
                    />
                );
    
            } else if (lastAction?.actionName === CONST.REPORT.ACTIONS.TYPE.POLICY_CHANGE_LOG.DELETE_INTEGRATION) {
                result.alternateText = `Removed connection to ${CONST.POLICY.CONNECTIONS.NAME_USER_FRIENDLY[ReportActionsUtils.getOriginalMessage(lastAction).connectionName]}`;
            } 
    

    and

    • The text to display can be updated later based on design.

    What alternative solutions did you explore? (Optional)

  3. melvin-bot commented on Aug 27, 2024

    @melvin-bot

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

  4. melvin-bot commented on Aug 29, 2024

    @melvin-bot

    Still overdue 6 days?! Let's take care of this!

  5. melvin-bot commented on Sep 2, 2024

    @melvin-bot

    10 days overdue. Is anyone even seeing these? Hello?

  6. added
    BugSomething is broken. Auto assigns a BugZero manager.
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 3, 2024
  7. melvin-bot commented on Sep 3, 2024

    @melvin-bot

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

  8. dylanexpensify commented on Sep 4, 2024

    @dylanexpensify
    Contributor

    @bfitzexpensify confirming this is a bug, yeah?

  9. bfitzexpensify commented on Sep 4, 2024

    @bfitzexpensify
    Contributor

    Yeah, I agree with the expected vs actual result differing, and this therefore being a bug

  10. melvin-bot commented on Sep 5, 2024

    @melvin-bot

    @dylanexpensify 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. 52 remaining items

  12. dylanexpensify commented on Oct 4, 2024

    @dylanexpensify
    Contributor

    Coming up!

  13. dylanexpensify commented on Oct 7, 2024

    @dylanexpensify
    Contributor

    Coming up!

  14. dylanexpensify commented on Oct 14, 2024

    @dylanexpensify
    Contributor

    Payment summary:

    Contributor: @daledah $250
    Contributor+: @DylanDylann $250

    Please apply/request!

  15. dylanexpensify commented on Oct 14, 2024

    @dylanexpensify
    Contributor

    @daledah please apply!

  16. dylanexpensify commented on Oct 14, 2024

    @dylanexpensify
    Contributor
  17. daledah commented on Oct 14, 2024

    @daledah
    Contributor
  18. dylanexpensify commented on Oct 16, 2024

    @dylanexpensify
    Contributor

    @daledah offer sent!

  19. DylanDylann commented on Oct 17, 2024

    @DylanDylann
    Contributor

    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:

    [@DylanDylann] The PR that introduced the bug has been identified. Link to the PR: *This change seem like a new feature, not a bug
    [@DylanDylann] 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: NA
    [@DylanDylann] 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: NA
    [@DylanDylann] Determine if we should create a regression test for this bug. Yes
    [@DylanDylann] 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.

    Regression Test Proposal

    1. Login with the same account in OD and ND
    2. Go to workspace in OD
    3. Connect to Quickbooks Dekstop
    4. In OD, disconnect from Quickbooks Desktop
    5. In ND, navigate to WS #admins chat
    6. Verify that: The Report Action Item, Sidebar Text shows the correct message
    7. Right click on the message, click "Copy to Clipboard" and paste.
    8. Verify that: Pasted text shows the correct message

    Do we agree 👍 or 👎

  20. dylanexpensify commented on Oct 17, 2024

    @dylanexpensify
    Contributor

    Done!

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded 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