Skip to content

[$500] Task - Chat is not scrolled to bottom when edit a task #38833

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.4.56-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: https://expensify.testrail.io/index.php?/runs/view/20318&group_by=cases:section_id&group_order=asc&group_id=291935
Email or phone of affected tester (no customers): shussain+web@applausemail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Open an existing chat
  2. Click the '+' > Assign Task
  3. Give the task as Title, Description and Assignee > Confirm Task
  4. Click on the created task in the chat
  5. Change the name > Save
  6. Verify there's an audit trail of the change in the chat thread
  7. Make more changes to the task (you can change the title, description, assignee) > click Save
  8. Verify that eventually the chat isn't fully scrolled to the bottom of last message (or audit trail change)

Expected Result:

Chat should always scroll to the bottom of the last message ( you should see the last message after making a change)

Actual Result:

After making multiple edits to a task, the chat thread isn't scrolled to the bottom.

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

Bug6423531_1711133132795.2024-03-22_23-44-10.mp4
2024-03-26_12-57-52.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01d64def74796adc96
  • Upwork Job ID: 1772488534557900800
  • Last Price Increase: 2024-03-26
  • Automatic offers:
    • fedirjh | Reviewer | 0
    • gijoe0295 | Contributor | 0

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 22, 2024
  2. melvin-bot commented on Mar 22, 2024

    @melvin-bot

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

  3. lanitochka17 commented on Mar 22, 2024

    @lanitochka17
    Author

    @Christinadobrzyn FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

  4. lanitochka17 commented on Mar 22, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #vip-vsp

  5. gijoe0295 commented on Mar 22, 2024

    @gijoe0295
    Contributor

    Proposal

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

    Chat is not scrolled to bottom when edit a task

    What is the root cause of that problem?

    Whenever there's any new report action in the report, we should call the notifyNewAction:

    function notifyNewAction(reportID: string, accountID?: number, reportActionID?: string) {

    to trigger scrollToBottom:

    InteractionManager.runAfterInteractions(() => reportScrollManager.scrollToBottom());

    That's what we've been doing for IOU requests (for eg here). But for edit task flow (editTask), we did not call it.

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

    Call Report.notifyNewAction(report.reportID, currentUserAccountID) after editing the task in editTask.

    We should also do it for whatever actions create new report action/message in the chat. For example: editTaskAssignee, reopenTask, completeTask.

    What alternative solutions did you explore? (Optional)

    NA

  6. bernhardoj commented on Mar 23, 2024

    @bernhardoj
  7. gijoe0295 commented on Mar 23, 2024

    @gijoe0295
    Contributor

    That's not correct @bernhardoj. This is a new behavior not on production and has different RCA with #38855.

  8. Christinadobrzyn commented on Mar 25, 2024

    @Christinadobrzyn
    Contributor

    Hum, I'm not able to reproduce this, it looks like the chat is at the bottom and the cursor is in the chat field when making edits to an assigned task.

    2024-03-25_11-36-13.mp4

    Asking QA for some clarification on the expected result vs actual result - https://expensify.slack.com/archives/C9YU7BX5M/p1711337939301019

  9. gijoe0295 commented on Mar 25, 2024

    @gijoe0295
    Contributor

    @Christinadobrzyn you need to scroll the task report up then make changes there. They expect that when there're new changes in that task report, it should scroll to bottom (just like regular chat report).

  10. Christinadobrzyn commented on Mar 26, 2024

    @Christinadobrzyn
    Contributor

    Ah okay, I think I'm able to reproduce, I updated the OP so it's clearer how to reproduce. I think this can be external and part of vip-vsb

  11. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Mar 26, 2024
  12. changed the title [-]Task - Chat is not scrolled to bottom when edit a task[/-] [+][$500] Task - Chat is not scrolled to bottom when edit a task[/+] on Mar 26, 2024
  13. 25 remaining items

  14. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Apr 2, 2024
  15. melvin-bot commented on Apr 2, 2024

    @melvin-bot

    📣 @fedirjh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job

  16. melvin-bot commented on Apr 2, 2024

    @melvin-bot

    📣 @gijoe0295 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

    Offer link
    Upwork job
    Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
    Keep in mind: Code of Conduct | Contributing 📖

  17. added
    ReviewingHas a PR in review
    and removed on Apr 2, 2024
  18. gijoe0295 commented on Apr 19, 2024

    @gijoe0295
    Contributor

    @Christinadobrzyn I think we're good for payment here because PR has been on production for nearly 10 days.

  19. Christinadobrzyn commented on Apr 22, 2024

    @Christinadobrzyn
    Contributor

    Thanks @gijoe0295 - not sure why the payment auto-message didn't trigger for this.

    Payouts due:

    Upwork job is here.

    @fedirjh or @gijoe0295 do we need a regression test for this?

  20. fedirjh commented on Apr 22, 2024

    @fedirjh
    Contributor

    @Christinadobrzyn It seems like this bug was discovered using a regression test. Please review the OP for more information:

    If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/runs/view/20318&group_by=cases:section_id&group_order=asc&group_id=291935

  21. Christinadobrzyn commented on Apr 22, 2024

    @Christinadobrzyn
    Contributor

    Ah thanks @fedirjh, if it was caught during a regression test then no payments should be made. I just requested a refund through Upwork for the payments sent earlier today. Let me know if I'm missing anything!

  22. fedirjh commented on Apr 22, 2024

    @fedirjh
    Contributor

    @Christinadobrzyn Sorry for the confusion. My above answer was related to this question :

    do we need a regression test for this?

    We don't need a regression test as we already have one listed in the OP.

    if it was caught during a regression test, then no payments should be made

    This is not the case for this issue. it is not caught during the regression period.

  23. Christinadobrzyn commented on Apr 23, 2024

    @Christinadobrzyn
    Contributor

    Oh thank you for clarifying! Okay, gotcha!

    Please ignore my refund requests. Closing since we don't need a regression. Let me know if I'm missing anything.

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.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in review

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions