-
Notifications
You must be signed in to change notification settings - Fork 3k
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 2023-11-22] [HOLD for payment 2023-11-21] [Payment due meow] Task - Description - When strikethrough is entered, the markdown is displayed incorrectly in the task description #31217
Comments
Not reproduce in production VID_20231111_033841.mp4 |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @chiragsalian ( |
This came from #27414. I think better to revert as it caused couple regressions (this one and #31199) |
thank you for that @aimane-chnaif. |
ok, happy to review and test PR |
The revert PR to review is here - #31219. I'll clean it up in the meantime. |
oops this is resolved. |
Reopened so I can resolve payment. Give me a min to do so @aimane-chnaif |
@aimane-chnaif, can you please accept the job and reply here once you have? |
@mallenexpensify accepted thanks |
Contributor+: @aimane-chnaif paid $500 via Upwork. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.98-5 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-11-21. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.99-0 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-11-22. 🎊 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:
|
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: 1.3.98.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:
fgjjjhExpected Result:
When strikethrough markdown is entered, same strikethrough markdown must be displayed in task description.
Actual Result:
When strikethrough is entered, the markdown is displayed incorrectly in the task description
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6271903_1699655121670.steike.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: