Task – Unable to edit description with a long link in existing task, error appears

[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.14-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4783737
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 chat with user B
4. Create a task assigned to another user with such description: https://staging.new.expensify.com/r/5730461601013640https://staging.new.expensify.com/r/5730461601013640
5. Open task detail
6. Click on description and edit it with a 2-3 characters

Expected Result:

Able to edit description

Actual Result:

Character limit exceeded (632/500) error appears

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

Bug6556612_1722283347261.Task_description.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @carlosmiceli

[melvin-bot]

Triggered auto assignment to @bondydaa (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[github-actions]

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

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[chiragsalian]

Doesn't look web-e related. Removing deployblocker label.

[bondydaa]

so this looks like we did it on purpose #43084

cc @carlosmiceli @abdulrahuman5196

[bondydaa]

I'm removing the blocker here, i think it was an intended behavior change from #42660.

[carlosmiceli]

@bondydaa to confirm, since we just implemented this behavior, we can assign this to External to fix the error message, right?

[bondydaa]

seems fine if that's whats needed but what is wrong with the error message?

[carlosmiceli]

No, my bad, got this one mixed up with the issue where there was an unintended error message shown to the user.