-
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
[HOLD for payment 2024-11-14] [$250] Task – Join thread option is present in context menu on deleted task with subtask #50566
Comments
Triggered auto assignment to @stephanieelliott ( |
@stephanieelliott 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 |
ProposalPlease re-state the problem that we are trying to solve in this issue.A join thread option shows for a task preview. What is the root cause of that problem?This not only happens with a deleted task, but just with a new task. When we create a new task, the notificationPreference is hidden. In this case, the App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx Lines 336 to 341 in 517ffaa
What changes do you think we should make in order to solve the problem?Add a check for task action, if it's a task action, don't show the join thread.
|
Job added to Upwork: https://www.upwork.com/jobs/~021844593880462626496 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Join thread option is present in context menu on deleted task with subtask What is the root cause of that problem?We have two problems here:
What changes do you think we should make in order to solve the problem?
Backend also needs to update the report's' `notificationPreference' in this case. What alternative solutions did you explore? (Optional) |
@stephanieelliott, @getusha Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Hey @getusha there are 2 proposals here, can you please review when you get a sec? |
@stephanieelliott, @getusha Eep! 4 days overdue now. Issues have feelings too... |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@stephanieelliott, @getusha 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@stephanieelliott, @getusha 10 days overdue. I'm getting more depressed than Marvin. |
Hey @getusha another bump, can you review the proposals here please? If I we don't hear from you today I'll post this in Slack to see if we can get someone else to take this one |
Why do we need this @nkdengineer it's not quite clear for me |
That's a different issue and already being handled here |
@bernhardoj's proposal looks good to me |
Triggered auto assignment to @grgia, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@stephanieelliott @grgia @getusha this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
Lil bump @grgia, wanna review the selected proposal when you get a sec/ |
Back from OOO, assigning |
PR is ready cc: @getusha |
PR is just awaiting internal review |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.58-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-11-14. 🎊 For reference, here are some details about the assignees on this issue:
|
@getusha @stephanieelliott The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
Payment Summary
BugZero Checklist (@stephanieelliott)
|
Requested in ND. |
Summarizing payment on this issue:
|
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.47-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Join thread option is not present
Actual Result:
Join thread option is present in context menu on deleted task with subtask, but not present on deleted task with a comment
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6630392_1728543980306.bandicam_2024-10-10_10-04-24-261.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @stephanieelliottThe text was updated successfully, but these errors were encountered: