Coming from this thread.
The onboarding tasks from Concierge to the user looks like this
This is the task pattern and if we did nothing, then it would look the same when these onboarding tasks move to the Expensify system user DM. But this looks very cluttered. For context, we envisioned the ideal design like so
Since Expensify system user chat and tasks are read-only, and we favor the uncluttered approach above, where the details are at the task level but not shown as threaded messages in the main chat - let's implement logic FE for all tasks created by the Expensify system user to hide the threaded messages in the main chat. a change where we move the task messages into the task description field as Jon outlined here. Full Figma examples here.
cc @mountiny @danielrvidal @dubielzyk-expensify
Upwork Automation - Do Not Edit
- Upwork Job URL: https://www.upwork.com/jobs/~0104bc3580ae719595
- Upwork Job ID: 1783858108561276928
- Last Price Increase: 2024-04-26
- Automatic offers:
- rayane-djouah | Contributor | 0
Issue Owner
Current Issue Owner: @twisterdotcom
Coming from this thread.
The onboarding tasks from Concierge to the user looks like this
This is the task pattern and if we did nothing, then it would look the same when these onboarding tasks move to the Expensify system user DM. But this looks very cluttered. For context, we envisioned the ideal design like so
Since Expensify system user chat and tasks are read-only, and we favor the uncluttered approach above, where the details are at the task level but not shown as threaded messages in the main chat - let's implement
logic FE for all tasks created by the Expensify system user to hide the threaded messages in the main chat.a change where we move the task messages into the task description field as Jon outlined here. Full Figma examples here.cc @mountiny @danielrvidal @dubielzyk-expensify
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @twisterdotcom