Repository navigation
Task - Task preview in Search shows incorrect message owner when task is assigned to self #38000
Description
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.49-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: https://expensify.testrail.io/index.php?/tests/view/4410340
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Precondition:
- User A and User B are in the same group chat.
- [User A] Create an unassigned task in the group chat.
- [User B] Go to the task report.
- [User B] Click assignee and assign to User B.
- {User B] Navigate back to group chat.
- [User B] Reopen the task report.
- [User B] Click Search.
Expected Result:
The preview for task report in Search for User B will display "User B: Assign to" since User B assigns the task to themselves.
Actual Result:
The preview for task report in Search for User B displays "User A: Assign to" when User B assigns the task to themselves.
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
Activity
github-actions commentedon Mar 8, 2024
👋 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:
melvin-bot commentedon Mar 8, 2024
Triggered auto assignment to @strepanier03 (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Mar 8, 2024
Triggered auto assignment to @francoisl (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.izarutskaya commentedon Mar 8, 2024
@strepanier03 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.
izarutskaya commentedon Mar 8, 2024
We think that this bug might be related to #vip-vsb
CC @quinthar
francoisl commentedon Mar 8, 2024
Discussed with @thienlnam, this is most likely at least partially backend-related so we're not going to block the deploy on this. Jack has an internal list of backend changes to make for tasks, we'll list this one there too.
melvin-bot commentedon Mar 8, 2024
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
francoisl commentedon Mar 19, 2024
Going to close this for now as it's already tracked in the issue linked above.