Skip to content

[Due for payment 2025-12-17] [$250] [RCA #74636] Task - Checkmark is only shown after reassigning assignee #75466

Closed

Description

@nlemma

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.2.60-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #74636
Email or phone of affected tester (no customers): sdoijnosdijdodjos@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Other

Action Performed:

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM.
  3. Create a task and assign the DM user as assignee.
  4. Open the task.
  5. Click Assignee.
  6. Select other assignee.

Expected Result:

In Step 5, after task is created, Assign list will show the assignee with checkmark.

Actual Result:

In Step 5, after task is created, Assign list does not show the assignee with checkmark.
It only shows the checkmark after reassign assignee.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug7007709_1763494929427.14.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021995474311928359736
  • Upwork Job ID: 1995474311928359736
  • Last Price Increase: 2025-12-01
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @bfitzexpensify

Activity

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

    @melvin-bot

    Triggered auto assignment to @johncschuster (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. melvin-bot commented on Nov 18, 2025

    @melvin-bot

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

  4. melvin-bot commented on Nov 18, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. changed the title [-]Task - Checkmark is only shown after reassigning assignee[/-] [+][RCA #74636] Task - Checkmark is only shown after reassigning assignee[/+] on Nov 19, 2025
  6. 60 remaining items

  7. melvin-bot commented on Dec 17, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@bfitzexpensify)

    • (if NewFeature) I have created a PR for any necessary HelpDot updates, or I confirmed no updates are necessary.
    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1995474311928359736/hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  8. mananjadhav commented on Dec 21, 2025

    @mananjadhav
    Collaborator

    BugZero Checklist:

    • [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: I think this wasn't addressed anytime during the implementation. I reported while working on a different PR. Not sure of the offending PR.

    • [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: NA

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

    I think we should add a regression test.

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

      Link to issue:

    Regression Test Proposal

    Test:

    1. Open 1:1 DM.
    2. Create a task and assign the DM user as assignee.
    3. Open the task.
    4. Click Assignee.
    5. Verify that the task's assignee is displayed with checkmark

    Do we agree 👍 or 👎

  9. mananjadhav commented on Dec 21, 2025

    @mananjadhav
    Collaborator

    @bfitzexpensify Checklist here ^

  10. JS00001 commented on Dec 22, 2025

    @JS00001
    Contributor

    Thanks! Waiting on @bfitzexpensify

  11. bfitzexpensify commented on Dec 22, 2025

    @bfitzexpensify
    Contributor

    Payment summary:

    @mananjadhav due $250 through NewDot Manual Requests
    @nkdengineer due $250 through NewDot Manual Requests

  12. twisterdotcom commented on Dec 23, 2025

    @twisterdotcom
    Contributor

    @nkdengineer has submitted payment for this report on ND here.

    SO: https://stackoverflowteams.com/c/expensify/questions/7582

    Zapier Logs Run ID: 00040eee-70c6-ae64-9cbe-e30240dcfe74
  13. trjExpensify commented on Dec 23, 2025

    @trjExpensify
    Contributor

    approved $250 for @mananjadhav

  14. mananjadhav commented on Dec 23, 2025

    @mananjadhav
    Collaborator

    Assuming it's already handled by @twisterdotcom here but @bfitzexpensify in this comment @nkdengineer is also required to be paid out.

  15. nkdengineer commented on Jan 20, 2026

    @nkdengineer
    Contributor

    Requested a negative amount to refund the duplicate request. reportID: 556762409793263

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

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions