Skip to content

[Due for payment 2025-08-18] [$250] Unable to Modify Assigned Task After User Leaves the Group Chat #65041

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.1.71-8
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: @NicMendonca
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

  1. In a group chat, assign a task to User A
  2. Have User A leave the group
  3. Attempt to edit or reassign the task as another member
  4. Observe that the task cannot be modified.

Expected Result:

If the assignee of a task leaves the group chat:
The task should remain editable by the person who has left the group if it is assigned to them

Actual Result:

Tasks assigned to users who have left the group become locked and uneditable.

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
2025-06-24_11-56-33.1.mp4
Recording.1342.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021939825548263273200
  • Upwork Job ID: 1939825548263273200
  • Last Price Increase: 2025-07-21
Issue OwnerCurrent Issue Owner: @AndrewGable

Activity

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

    @melvin-bot

    Triggered auto assignment to @lydiabarclay (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. abzokhattab commented on Jun 26, 2025

    @abzokhattab
    Contributor

    Not reproducable on my side

  4. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    @lydiabarclay Whoops! This issue is 2 days overdue. Let's get this updated quick!

  5. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    @lydiabarclay Whoops! This issue is 2 days overdue. Let's get this updated quick!

  6. lydiabarclay commented on Jun 30, 2025

    @lydiabarclay
    Contributor

    will review asap

  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Jun 30, 2025
  8. changed the title [-]Unable to Modify Assigned Task After User Leaves the Group Chat[/-] [+][$250] Unable to Modify Assigned Task After User Leaves the Group Chat[/+] on Jun 30, 2025
  9. melvin-bot commented on Jun 30, 2025

    @melvin-bot
  10. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Jun 30, 2025
  11. 53 remaining items

  12. Shahidullah-Muffakir commented on Jul 31, 2025

    @Shahidullah-Muffakir
    Contributor

    PR is ready for review
    CC: @suneox

  13. Shahidullah-Muffakir commented on Aug 16, 2025

    @Shahidullah-Muffakir
    Contributor

    Hi @lydiabarclay
    It's ready for payment, as it was deployed to prod on 7th, thanks!

  14. lydiabarclay commented on Aug 18, 2025

    @lydiabarclay
    Contributor

    @suneox can you please fill out the bz checklist?

  15. changed the title [-][$250] Unable to Modify Assigned Task After User Leaves the Group Chat[/-] [+][Due for payment 2025-08-18] [$250] Unable to Modify Assigned Task After User Leaves the Group Chat[/+] on Aug 18, 2025
  16. suneox commented on Aug 18, 2025

    @suneox
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    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:

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] 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: https://github.com/Expensify/App/pull/60869/files#r2282967499

    • [Contributor] 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: N/A

    • [Contributor] 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.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/537300

    Regression Test Proposal

    Precondition:

    • Create a group chat between User A & User B

    Test:

    1. In a group chat, User A assign a task to User B
    2. User B leaves the group

    Verify after User B leaves the group chat the assigned task to User B from step 1 can still be edited by User A & B

    Do we agree 👍 or 👎

  17. lydiabarclay commented on Aug 18, 2025

    @lydiabarclay
    Contributor
  18. lydiabarclay commented on Aug 18, 2025

    @lydiabarclay
    Contributor

    Payment Summary

    Contributor: @Shahidullah-Muffakir paid $250 via Upwork
    Contributor+: @suneox due $250 via NewDot

    ✅ Regression test filed

  19. trjExpensify commented on Sep 1, 2025

    @trjExpensify
    Contributor

    Approved $250 for @suneox

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

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions