You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-03-07] [$125] Web - Thread - Console error shows up when opening message in thread #37253
Version Number: 1.4.44-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: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: Applause - Internal Team Slack conversation:
Action Performed:
Go to staging.new.expensify.com
Go to any chat
Send a message
Right click on the message > Reply in thread
Expected Result:
No console error will show up
Actual Result:
Console error shows up when opening message in thread
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]Web - Thread - Console error shows up when opening message in thread[/-][+][$500] Web - Thread - Console error shows up when opening message in thread[/+]on Feb 27, 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:
Identify the pull request that introduced this issue and revert it.
@youssef-lr@techievivek Hi I see after this comment, you've downgraded the issue bounty to $125, I assume that's because the change suggested is tiny, just adding the ? to avoid undefined object access.
However that "quick change" is a workaround. The root cause and solution of this issue is actually different and more complex (see here), and that's what we went with to fix the issue (with urgency as it was a deploy blocker).
Could we honor the original bounty ($500) for the issue since it was not dead simple as initially suggested?
@dukenv0307 I think I lowered the bounty due to this being just a console error and it's not really affecting the user. Do you think the console error is a smoke for an actual bug in the UI that is noticeable by the user?
Activity
[-]Web - Thread - Console error shows up when opening message in thread[/-][+][$500] Web - Thread - Console error shows up when opening message in thread[/+]melvin-bot commentedon Feb 27, 2024
Job added to Upwork: https://www.upwork.com/jobs/~01fd70450a1c9c7c93
melvin-bot commentedon Feb 27, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (
External)github-actions commentedon Feb 27, 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 Feb 27, 2024
Triggered auto assignment to @techievivek (
Engineering), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.lanitochka17 commentedon Feb 27, 2024
We think that this bug might be related to #vip-vsp
CC @quinthar
31 remaining items
MitchExpensify commentedon Mar 9, 2024
Payment summary:
C+: $125 @sobitneupane (NewDot)
C: $125 @dukenv0307 (Upwork)
I couldn't find any older contract for you @dukenv0307 so I created this job, let me know when you've accepted the offer and I'll issue payment 🙇 https://www.upwork.com/jobs/~016662aefe6aa80518
techievivek commentedon Mar 12, 2024
Not overdue, we are issuing the payments. CC @MitchExpensify
dukenv0307 commentedon Mar 12, 2024
@youssef-lr @techievivek Hi I see after this comment, you've downgraded the issue bounty to $125, I assume that's because the change suggested is tiny, just adding the
?to avoid undefined object access.However that "quick change" is a workaround. The root cause and solution of this issue is actually different and more complex (see here), and that's what we went with to fix the issue (with urgency as it was a deploy blocker).
Could we honor the original bounty ($500) for the issue since it was not dead simple as initially suggested?
MitchExpensify commentedon Mar 12, 2024
Waiting on @dukenv0307 to accept the offer in order to pay 🙇
youssef-lr commentedon Mar 12, 2024
@dukenv0307 I think I lowered the bounty due to this being just a console error and it's not really affecting the user. Do you think the console error is a smoke for an actual bug in the UI that is noticeable by the user?
MitchExpensify commentedon Mar 17, 2024
Bump on accepting this offer as a next step @dukenv0307 https://www.upwork.com/nx/wm/offer/101299289
dukenv0307 commentedon Mar 18, 2024
Thanks for the explanation.
@MitchExpensify I accepted, thank you!
MitchExpensify commentedon Mar 19, 2024
Paid and contract ended 🙇
sobitneupane commentedon Mar 21, 2024
Requested payment in newDot.
Payment Summary: #37253 (comment)
JmillsExpensify commentedon Mar 22, 2024
$125 approved for @sobitneupane based on summary.