[$250] Threads - Hmm... it's not here page is shown when using the link of a message

[lanitochka17]

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.60-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): dave0123seife+adf41@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Start a chat/Go to any chat
2. Send a message
3. Write click on the message body and click on copy ink
4. Create a thread on the message sent
5. Paste the Link copied on the thread created
6. Click on the link pasted
   Notice that when clicking the link it takes you back to the Parent Conversation highlighting the parent message
7. Now go to the same thread, right-click on the Parent message that is in the thread, and Copy link
8. Paste the copied link to the composer and send it
9. Click on the link pasted. Notice that Hmm... it's not here page is shown
   Note: Using the link of the Parent message that is in the thread anywhere results in Hmm... it's not here page, being displayed

Expected Result:

Able to use the link of the Parent message that is in the thread

Actual Result:

Using the link of the Parent message, that is in the thread, anywhere results in Hmm... it's not here page, being displayed

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

Bug6438138_1712245439074.Issue_on_Copy_Link.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0100f8db9a0c05cca8
• Upwork Job ID: 1779873465345101824
• Last Price Increase: 2024-04-15

[melvin-bot]

Triggered auto assignment to @muttmuure (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[lanitochka17]

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

[lanitochka17]

We think that this bug might be related to #vip-vsp

[nkdengineer]

Proposal

Please re-state the problem that we are trying to solve in this issue.

• Threads - Hmm... it's not here page is shown when using the link of a message

What is the root cause of that problem?

• In here, the reportID points to the current thread report ID, not a parent reportID, that leads to the report action link is not correct, so the "It's not here" is displayed in this case.

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

• We can update this to:

                const report = ReportUtils.getReport(reportID);
                const parentReportActionID = report.parentReportActionID;
                let targetReportID = reportID;

                if (parentReportActionID && reportActionID === parentReportActionID) {
                    targetReportID = report.parentReportID;
                }
                Clipboard.setString(`${environmentURL}/r/${targetReportID}/${reportActionID}`);

so, if the report action is parent report action, use the parent report ID instead of current report ID

What alternative solutions did you explore? (Optional)

• NA

[melvin-bot]

@muttmuure Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[muttmuure]

Handling tomorrow

[melvin-bot]

Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Current assignee @akinwale is eligible for the External assigner, not assigning anyone new.

[FitseTLT]

This is dupe

[muttmuure]

Closing dupe

[nkdengineer]

@muttmuure I do not think it is a dupe of #36057 because currently, I cannot reproduce that bug

[FitseTLT]

@muttmuure I do not think it is a dupe of #36057 because currently, I cannot reproduce that bug

If you can't reproduce that bug then you can't reproduce this one. Both are the same issues and hence reproducible.

[nkdengineer]

I can reproduce this one in staging. Please correct me if I miss any step:

Screen.Recording.2024-04-15.at.22.01.04.mov

[FitseTLT]

@nkdengineer It is the Actual Result that is confusing you, it is because of the time difference between the creation of the two issues but the expected behaviour is same for both; the parent message highlighted on the current thread same as comment linking behaves in all other cases.

[nkdengineer]

@FitseTLT Thanks for your information