No system message when editing a task

[kavimuru]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Action Performed:

1. Create a task and add assignee
2. Reassign the task to someone

Expected Result:

Should include a system message indicating that it was reassigned

Actual Result:

There is no message

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.43-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

Recording.1296.mp4

Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689744951886999

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~01ecf0cd51093fcffd
• Upwork Job ID: 1682151598616768512
• Last Price Increase: 2023-07-20

[melvin-bot]

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

[melvin-bot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[thienlnam]

This will have to be a mix of internal and external (We're currently not showing any system message when you edit the task, but we can surface that and include what was changed)

[MitchExpensify]

Reproduced (Task was originally assigned to Franc)

[MitchExpensify]

This will have to be a mix of internal and external

What label do you recommend @thienlnam ?

[thienlnam]

This is actually a new feature, so let's make it internal first until we're ready to update the front-end

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~01ecf0cd51093fcffd

[melvin-bot]

Triggered auto assignment to Contributor Plus for review of internal employee PR - @s77rt (Internal)

[melvin-bot]

Current assignee @MitchExpensify is eligible for the NewFeature assigner, not assigning anyone new.

[thienlnam]

Can handle the internal updates

[thienlnam]

We're making some changes to the assignee flow for this internal issue https://github.com/Expensify/Expensify/issues/299956 (Related to the privacy changes we need to make)

So let's hold this PR on that, so we don't have to re-do any of the work there

[MitchExpensify]

Still on hold for https://github.com/Expensify/Expensify/issues/299956

[MitchExpensify]

Still on hold for https://github.com/Expensify/Expensify/issues/299956

Same

[MitchExpensify]

How is the PR coming along at this point @thienlnam ?

[thienlnam]

Haven't gotten started on this yet - though the linked issue https://github.com/Expensify/Expensify/issues/299956 is about to be wrapped up so I can start on this soon

[thienlnam]

We still want to do this for consistency but it's not really a priority right now so I bumped to a monthly

[MitchExpensify]

This doesn't fall into a wave IMO, do you agree @thienlnam ?

[thienlnam]

This was being handled under VSB - finish tasks, but not part of a wave

[thienlnam]

We didn't finish this by EOY - need to see if we still want to do this

[thienlnam]

Spun up a BE PR, after that we can have a contributor handle the FE changes

[thienlnam]

Web-E PR merged, need to create a new implementation issue for App

[MitchExpensify]

need to create a new implementation issue for App

Are you on the case for this @thienlnam ?

[thienlnam]

Ah, I created one here #36196 (comment)

Wait.. you're assigned to it as well 😆
I'll close this one so we can consolidate there