-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$500] Task - Canceled task disappears from the conversation #28658
Comments
Triggered auto assignment to @isabelastisser ( |
Bug0 Triage Checklist (Main S/O)
|
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @deetergp ( |
Job added to Upwork: https://www.upwork.com/jobs/~017d268a31fa534112 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
How to reproduce this locally? |
ProposalPlease re-state the problem that we are trying to solve in this issue.Canceled task disappears from the conversation What is the root cause of that problem?We're excluding The cancelled task satisfies that condition so it also disappears. This is incorrect since we still want to show cancelled task because we still keep the thread for it in the LHN, so it'll be confusing to the user when they go back from the thread to the parent report and do not see any task-related information. What changes do you think we should make in order to solve the problem?Update this condition to allow cancelled tasks to be visible Like below
We might need to modify the optimistic data when cancelling the task for it to show accordingly in LHN as well. What alternative solutions did you explore? (Optional)NA |
Isn’t this an expected behavior for the [Deleted task] to disappear from the conversation? That way, it would be consistent with how threads behave. |
Proposalissue: |
📣 @pasala-krishna! 📣
|
Contributor details |
I wonder how you're able to test this locally? Because I wasn't able to reproduce it. |
@dukenv0307 Thanks for the proposal, reminding that if the issue is a deploy blocker, lets always link the offending PR. Looking at this again though, I am not sure if this is intended or no, probably ont but does not feel like a blocker. @thienlnam from this PR #28128 might have better idea what the expected behaviour is here |
Yeah this is intended in some situations, we've also been discussing this in this issue, so I'm going to close this to consolidate the discussion there |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
The task is unmarked in the 1:1 chat where the task was shared
Actual Result:
Canceled task disappears from the conversation
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.76-1
Reproducible in staging?: Yes
Reproducible in production?: No
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
Notes/Photos/Videos: Any additional supporting documentation
Bug6222520_1696282489506.Canceled_task.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: