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 2023-08-28] [$1000] When in editing mode, the edited message does not dynamically update between the main chat and sub-thread #22368
Hover on the message X at step 2 and select the “Reply in thread” option
Inside the thread, hover on X and select the “Edit” option but leave it here, DO NOT save
Click the link on the chat report header to go back to “Main chat”
Hover on X again, select the Edit option, change the message to Y and Save
Hover on the edited message (now it became Y) and select “Reply in thread” again
Expected Result:
The pending edit text should be updated to Y (since the message ID is still the same)
Actual Result:
Pending edit text still showing as the old text - X
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android / native
Android / Chrome
iOS / native
iOS / Safari
MacOS / Chrome / Safari
MacOS / Desktop
Version Number: 1.3.37-2 Reproducible in staging?: y Reproducible in production?: y 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
changed the title [-][$1000] When in editing mode, the edited message does not dynamically update between the main chat and sub-thread[/-][+][HOLD for payment 2023-08-28] [$1000] When in editing mode, the edited message does not dynamically update between the main chat and sub-thread[/+]on Aug 21, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.55-8 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 2023-08-28. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
For reference, here are some details about the assignees on this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@mollfpr] The PR that introduced the bug has been identified. Link to the PR:
[@mollfpr] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[@mollfpr] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[@mollfpr] Determine if we should create a regression test for this bug.
[@mollfpr] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@sophiepintoraetz] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Issue Reporter: $250 @tranvantoan-qn - Paid
Contributor: $1000 @dukenv0307 (Assigned 28 Jul - submitted for review on 1 Aug) so I don't think this is eligible for the urgency bonus given the comment review but neither is it eligible for the penalty.
Contributor+: $1000 @mollfpr (I'll release payment once the checklist is done)
[@mollfpr] The PR that introduced the bug has been identified. Link to the PR:
[@mollfpr] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
No offending PR. We haven't implemented the sync between parent and child on the report action draft.
[@mollfpr] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
The regression step should be enough.
[@mollfpr] Determine if we should create a regression test for this bug.
[@mollfpr] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
Login to an account
Send a message - X
Hover on the message X at step 2 and select the “Reply in thread” option
hover on X and select the “Edit” option inside the thread, but leave it here. DO NOT save
Click the link on the chat report header to go back to “Main chat”
Hover on X again, select the Edit option, change the message to Y and Save
Hover on the edited message (now it became Y) and select “Reply in thread” again
Verify that The pending edit text should be updated to Y (since the message ID is still the same)
Select Edit message X but not save
Go to the thread of that message, then change the message to Z and Save
Verify that The pending edit text should be updated to Z (since the message ID is still the same)
Activity
melvin-bot commentedon Jul 6, 2023
Triggered auto assignment to @sophiepintoraetz (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Jul 6, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)sophiepintoraetz commentedon Jul 11, 2023
This is not reproducible on v1.3.39-5 @tranvantoan-qn? (I'm on staging)
2023-07-11_13-02-18.mp4
tranvantoan-qn commentedon Jul 11, 2023
Hi @sophiepintoraetz

It is still happening.
The steps to reproduce it is quite many and we need to do the exact steps
sophiepintoraetz commentedon Jul 11, 2023
@tranvantoan-qn if there are many steps, please can you make sure that they are fully captured in the reproduction steps?
tranvantoan-qn commentedon Jul 11, 2023
Yes, each step and its explanation is fully captured in the attached video above
I post the video here again
251550670-3a6600c7-3f53-44d9-b806-00fa944ac66d.mp4
sophiepintoraetz commentedon Jul 11, 2023
Let me upload the correct video but please can you confirm which steps aren't being completed - I am well aware of the video in the master GH.
https://github.com/Expensify/App/assets/42940078/26492833-b4db-4437-801a-c648043f234d
61 remaining items
[-][$1000] When in editing mode, the edited message does not dynamically update between the main chat and sub-thread[/-][+][HOLD for payment 2023-08-28] [$1000] When in editing mode, the edited message does not dynamically update between the main chat and sub-thread[/+]melvin-bot commentedon Aug 21, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Aug 21, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.55-8 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 2023-08-28. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
melvin-bot commentedon Aug 21, 2023
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
sophiepintoraetz commentedon Aug 28, 2023
Payouts due:
Issue Reporter: $250 @tranvantoan-qn - Paid
Contributor: $1000 @dukenv0307 (Assigned 28 Jul - submitted for review on 1 Aug) so I don't think this is eligible for the urgency bonus given the comment review but neither is it eligible for the penalty.
Contributor+: $1000 @mollfpr (I'll release payment once the checklist is done)
Eligible for 50% #urgency bonus? N
sophiepintoraetz commentedon Aug 29, 2023
Bump @mollfpr!
mollfpr commentedon Aug 29, 2023
Sorry for the delay!
No offending PR. We haven't implemented the sync between parent and child on the report action draft.
The regression step should be enough.
sophiepintoraetz commentedon Aug 30, 2023
Payment released, regression test added.