[$250] Task – Join thread option is present in context menu on deleted task with subtask

[lanitochka17]

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:

1. Go to https://staging.new.expensify.com/
2. Log in
3. Open any chat
4. Create a task
5. Open task details and create a subtask
6. Click on the header and delete task
7. Go back to main chat and right click on the deleted task

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?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

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

• Upwork Job URL: https://www.upwork.com/jobs/~021844593880462626496
• Upwork Job ID: 1844593880462626496
• Last Price Increase: 2024-10-18

Issue Owner

Current Issue Owner: @getusha

[melvin-bot]

Triggered auto assignment to @stephanieelliott (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.

[lanitochka17]

@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

[bernhardoj]

Proposal

Please 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 subscribed is false and we don't have any condition to check whether it's a task or not, so the Join thread is shown.

App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx

Lines 336 to 341 in 517ffaa

	const subscribed = childReportNotificationPreference !== 'hidden';
	const isThreadFirstChat = ReportUtils.isThreadFirstChat(reportAction, reportID);
	const isWhisperAction = ReportActionsUtils.isWhisperAction(reportAction) || ReportActionsUtils.isActionableTrackExpense(reportAction);
	const isExpenseReportAction = ReportActionsUtils.isMoneyRequestAction(reportAction) || ReportActionsUtils.isReportPreviewAction(reportAction);
	return !subscribed && !isWhisperAction && !isExpenseReportAction && !isThreadFirstChat && (shouldDisplayThreadReplies || (!isDeletedAction && !isArchivedRoom));
	},

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.

const isTaskAction = ReportActionsUtils.isCreatedTaskReportAction(reportAction);
return !subscribed && !isWhisperAction && !isTaskAction && ...;

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021844593880462626496

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @getusha (External)

[nkdengineer]

Proposal

Please 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:

1. The Join button is also shown when we create the task. The RCA is we don't have any condition here to prevent showing the join button if the action is created task action

const isTaskCreatedAction = ReportActionsUtils.isCreatedTaskReportAction(reportAction);
return !subscribed && !isWhisperAction && !isExpenseReportAction && !isThreadFirstChat && !isTaskCreatedAction && (shouldDisplayThreadReplies || (!isDeletedAction && !isArchivedRoom));

App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx

Line 340 in 4c90d62

return !subscribed && !isWhisperAction && !isExpenseReportAction && !isThreadFirstChat && (shouldDisplayThreadReplies || (!isDeletedAction && !isArchivedRoom));

2. The Join button is still shown if we create a task in the task report. In this case, I think the current problem is the notificationPreference is still hidden after we create a task in the task report.

What changes do you think we should make in order to solve the problem?

1. We should add a check not to show the join button if the action is the created task action

App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx

Line 340 in 4c90d62

return !subscribed && !isWhisperAction && !isExpenseReportAction && !isThreadFirstChat && (shouldDisplayThreadReplies || (!isDeletedAction && !isArchivedRoom));

2. When we create a new task, we should check if the notificationPreference is hidden, we should update this and update childReportNotificationPreference of the parent report action to always

Backend also needs to update the report's' `notificationPreference' in this case.

What alternative solutions did you explore? (Optional)

[melvin-bot]

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

[stephanieelliott]

Hey @getusha there are 2 proposals here, can you please review when you get a sec?

[stephanieelliott]

Hey @getusha there are 2 proposals here, can you please review when you get a sec?

^^ Bump on this @getusha

[melvin-bot]

@stephanieelliott, @getusha Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@stephanieelliott, @getusha 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[melvin-bot]

@stephanieelliott, @getusha 10 days overdue. I'm getting more depressed than Marvin.

[stephanieelliott]

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

[getusha]

When we create a new task, we should check if the notificationPreference is hidden, we should update this and update childReportNotificationPreference of the parent report action to always

Why do we need this @nkdengineer it's not quite clear for me

[bernhardoj]

That's a different issue and already being handled here

[getusha]

@bernhardoj's proposal looks good to me
🎀 👀 🎀 C+ Reviewed

[melvin-bot]

Triggered auto assignment to @grgia, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

[melvin-bot]

@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!

[stephanieelliott]

Lil bump @grgia, wanna review the selected proposal when you get a sec/