Tim Jasper: Thanks for the feedback here! We have syncing in progress soon, which will help the situations you're describing!

Philipp Berner thinking of when I chat someone real quick on a question that's related to a task, I'd like to be able to see that chat message within the chat when applicable.

In an ideal world, I'm commenting directly in the task but if I use chat instead for a faster response, would be good to associate that message with the chat after the fact

Philipp Berner #3 is preferred over #2 for me. Typically when I'm sharing a task link to a Chat thread it's a "Hey, I created an actionable item for this conversation" or "We are already tracking this here". Adding the relationship provides a quick way for me to reference where these conversations have happened and how many times it's coming up.

#1 would also be great but needs to be handled smoothly. I see this as an opt-in rather than automatic.

Duncan Owen: Can you expand on the use case for me on linking a entire channel to a Task. Where and how would that help your workflow.

Sure Philipp Berner . Our setup is space (business area), folder (client), list (data repository or area for tasks).

Two use cases:

1) In the data repository list, we have a budget task (at a client level). The task contains any information about client budgets, but discussion about coming budgets or messages to the team could be had in chat format.

2) In the actionable tasks list, let's say we're onboarding a new client, and have a primary onboarding SoP task, with a raft of subtasks for different team members. Chat around onboarding would be great to have linked just to that specific period of time - rather than in the general client chat channel.

Philipp Berner You ClickUp people really need to get a clue about how the real world works. Specifically these sales bro run companies - which is basically 89.8% of all companies.

These guys can figure out & use email. Same goes for Slack/texting. They absolutely, without question, _will_not_ go clicking around in an app

So my employer manufactures & markets exercise equipment. Our projects are MASSIVE undertakings with tons of moving parts. Almost all departments are involved in almost all aspects of a project. And we have dozens of products & are developing dozens more.

We [would have] tasks dealing with design, development, engineering, testing, packaging, instruction manuals, app development (and everything that goes along with all of that), branding, markings, labels, shipping and logistics, customer service issues, and more. Each one of those tasks [would have] lots and lots of discussion within them.

A folder level chat would just get wwwaaaaaaaayyy too clogged up with tooo much info to sort through.

But there's no way you can count on sales bros to go clicking around in an app they don't want to use looking for some Chat in some Space in some Folder in some List in some Task from two months ago.

Not going to happen.

If - Big IF - you could even get Sales Bros to use ClickUp at all, we're going to have to get any chat to their eyeballs in three taps MAX. That means:

• Option to set Chat View as default view on mobile.

• Have task Chats port into Chat View.

• Isolated Chat Search when in Chat View.

• Essentially look/work/act like a basic Chat App - nothing more.

All the Space/Folder/List/Group/Team Chats are great & all, but we need Sales Bros to be able to pop into the "Drop Testing For Shitty New Treadmill" or the "Rebranded Packaging For Cheap, Shitty Old Elliptical" task chat in under three taps. Otherwise Chat's not going to fly for us.

Michael In your screenshot, can you please explain what you're recommending?

Totally hear you on the other stuff; but I'm curious why do you need "chat" for tasks when a task is already essentially a chat (with comments feed etc)?

Zeb!!! Well that escalated quickly! Hope you had a great Thanksgiving buddy!

Sorry if I was confusing - all I'm really saying, which I this request is also asking for, is that task chats also appear in the #ChatView. I get that Slack and these "Other Chat Apps" kinda corral chats by broader categories like "Teams" and "Projects", but for the company I work at ("developing" fitness equipment) the projects are HUGE. So yeah you can assign a comment and mention tasks and all that, but Sales Bros just don't do that.

For example: We're developing four very similar products all at once. Each has to go through it's own testing. These are four separate already active tasks. If we try to discuss all the details of all four of these similar-but-different products in the "engineering" chat, we're back to email pandemonium where products get confused with one another, not to mention intermixed with the testing requirements of 17 other products and a zillion other engineering discussions.

Even the engineering list chat for the specific product is going to get a little messy. It's fine for now (especially since my employer isn't currently using ClickUp), but we'll have an email chain literally hundreds of replies long just on one little issue.

That's why it would be much better just to have the task chat in the #ChatView. Then when it's behind us, it drift... drift... drifts to the bottom never to be seen again.

As far as my screenshot, the point is mainly that there's way too much going on. You've really gotta get in the head of the Sales Bro. Like, three buttons. Four MAX. Right now you've got THIRTEEN. More if you scroll. search fields?! GTFOoH! Those "Reply" "Post" "Activity" buttons can be chopped in half height-wise if you to keep them, but you really don't need them. And if you can't give SalesBros™ the ability to set #ChatView as the default view, at least move the "Chat" button closest to the thumb.

Well anyway, you're much busier than I am so I'll end my rant! But I do love the new #Chat! Nice work - now just pipe in the Task Chats, maybe do a button audit & you've just about got it!

Michael thanks for the feedback. I'm passing this on to Brendan W who is now the product owner of chat

Michael Super helpful thank you for the feedback! And always keep it coming. We'll put our heads together and work on a solution!

This just happened AGAIN yesterday Zeb & Philipp Berner! Two identical products being discussed in the same email chain.

Someone on my team requested the final files I had been working on. But because the email title was that of one of them, I provided those files. But she was actually requesting the files for , nearly identical model! But the files are different between the two.

It wasn't big of a deal, but the factory was copied which obviously compounds the confusion. And if no one had caught it, we could have produced some incorrectly causing a costly re-work.

Not only that, but simply the time of the back and forth emails for days and days adds up. When if we had just had separate task chats for the different products, none of that would have ever been an issue. And if we could have seen those task chats in #ChatView, it would have been allthemore easier.

Anyway, just another little nugget as I try to get my employer back on ClickUp!