Skip to content

[HOLD #30668] [$500] Chat - Unpinned deleted tasks assigned by another user are shown above other pinned messages #30798

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.95-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. Login with Account A on new Expensify and assign a task to Account B
  2. Cancel the task
  3. Login with Account B > find the Deleted task in the LHN
    Tester login credential: gatantm+82@gmail.com gatantm+112@gmail.com
  4. If you don't see it above the pinned messages, click on the [Deleted task] message again and eventually it displays above the pinned chats

Expected Result:

Unpinned messages appear under pinned chats on LHN

Actual Result:

In the new build the Assigned tasks from another account that were canceled appear above or between pinned messages when they were never pinned

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

2023-11-02_16-42-06.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01f5bd596fa8bc9e1a
  • Upwork Job ID: 1721590933982339072
  • Last Price Increase: 2023-11-06
  • Automatic offers:
    • s77rt | Reviewer | 27545058

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Nov 2, 2023

    @melvin-bot

    Bug0 Triage Checklist (Main S/O)

    • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
    • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
      • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
    • This bug is reproducible using the reproduction steps in the OP. S/O
      • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
      • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
    • This issue is filled out as thoroughly and clearly as possible
      • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
    • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync
  4. OSBotify commented on Nov 2, 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 2, 2023

    @melvin-bot

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

  6. kbecciv commented on Nov 2, 2023

    @kbecciv

    @Christinadobrzyn Can you create a task and assign it to user B using the 'share somewhere' option?

  7. Christinadobrzyn commented on Nov 2, 2023

    @Christinadobrzyn
    Contributor

    I can reproduce with the steps in the OP. @kbecciv Should I also test the share somewhere option for this?

  8. Christinadobrzyn commented on Nov 2, 2023

    @Christinadobrzyn
  9. 90 remaining items

  10. DylanDylann commented on Dec 13, 2023

    @DylanDylann
    Contributor

    @Christinadobrzyn @s77rt This PR is merged. Let's remove hold

  11. DylanDylann commented on Dec 13, 2023

    @DylanDylann
    Contributor

    After re-check on the latest main, I see that after canceling the task the GRB still displays

    bug.mp4

    From my viewpoint, I think the GRB should disappear immediately after canceling the task

    So that I post this proposal to fix this bug

    Proposal

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

    After canceling the task the GRB still displays on LHN

    What is the root cause of that problem?

    After canceling the task the GRB still displays on LHN, The pusher return taskReport.isDeletedParentAction === true . But we don't add this field in this function

    function getOptionData(

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

    in this function

    function getOptionData(

    we should return isDeletedParentAction

        result.isDeletedParentAction = report.isDeletedParentAction;
    
    

    We also need to do the same thing in the chat report selector here

    parentReportID: report.parentReportID,

    should add

            isDeletedParentAction: report.isDeletedParentAction
    
    

    What alternative solutions did you explore? (Optional)

    NA

    Result

    sol.mp4
  12. s77rt commented on Dec 13, 2023

    @s77rt
    Member

    @DylanDylann This issue does not have Help Wanted label. @waterim is already assigned to work on this issue

  13. s77rt commented on Dec 13, 2023

    @s77rt
    Member

    @Christinadobrzyn Please lift the hold since #32140 is merged now

  14. s77rt commented on Dec 13, 2023

    @s77rt
    Member

    @waterim Please check this issue once you get a chance

  15. waterim commented on Dec 14, 2023

    @waterim
    Contributor

    @s77rt I can see that the issue here is "Unpinned deleted tasks assigned by another user are shown above other pinned messages", but this one was fixed and as I understand we want to fix GBR for deleted task as well here, right?

  16. DylanDylann commented on Dec 14, 2023

    @DylanDylann
    Contributor

    @s77rt @Christinadobrzyn Should we create a new issue for the bug that is mentioned here ? I think It also be a critical bug

  17. waterim commented on Dec 14, 2023

    @waterim
    Contributor

    @s77rt After my check I agree with @DylanDylann solution, we are just not setting in time the data regarding "isDeletedParentAction" when pusher sends it to us. I can create a PR for that

  18. s77rt commented on Dec 15, 2023

    @s77rt
    Member

    Since this is another bug I think it would be fair to create another issue for it.

  19. s77rt commented on Dec 15, 2023

    @s77rt
    Member

    For this one I think we can just close it.

  20. DylanDylann commented on Dec 15, 2023

    @DylanDylann
    Contributor

    @Christinadobrzyn @lanitochka17 Could you help to create a new issue for this one. It is so similar this issue and it is critical bug

    Action Performed:
    Same as this issue

    Expected Result:
    The deleted task report should not appear between GRB reports

    Actual Result:
    The task report still appears between GRB reports and GRB appear in the deleted task report

    Video

    bug.mp4

    cc @s77rt

  21. Christinadobrzyn commented on Dec 22, 2023

    @Christinadobrzyn
    Contributor

    So sorry for the delay @DylanDylann I created the new issue here- #33477

    should we close this one or work on them together?

  22. s77rt commented on Dec 22, 2023

    @s77rt
    Member

    @Christinadobrzyn This can be closed

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.EngineeringExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions