Support hashtags in channels and DMs
Allow clickable links on #hashtagged items ... in a channel or group, perform a search within that group.
For DMs and conversations, search all of your conversations
Sean McHugh
shared this idea
This feature is on the backlog. I will update you when we have more details to share.
323 comments
-
Joe
commented
While this might not seem like a huge priority, it is a viable short term alternative to the very important problem of organizing communication for teams with lots of projects, and would allow a team to manage multiple threads for multiple projects in a single channel (attaching communication by hashtag instead). There are a pile of OSS libraries for hashtag autocomplete on Github, is this really moving heaven and earth to get this implemented?
-
Fabrizio Pavoni
commented
Any feedback on this request @Alex?
-
Anonymous
commented
This should be combined with the ability to hashtag in the chat during a recording and have it bring you to that point in the recording.
-
Pete Simpkins
commented
These tags could be similar or the same as the organization's Yammer tags and ultimately tie out to Project Cortex topic cards.
-
Anonymous
commented
how is it that your competitor can roll out functions like this at the drop of a hat yet it takes MS 4 years and its still not done.. is slack just a better product? this is kind of ridiculous
-
Duncan
commented
Could be a hashtag, but might work better with pre-set "tags" or "categories", (This gets round the issue of various different hashtags actually referring to the same thing eg #project vs #project_1 which likely refer to the same thing but are different hashtags).
So you could eg set up a "category" for Project 1 for user to 'tag' messages, and then have this easily searchable
-
Anonymous
commented
We have records retention requirements. Sometimes this includes conversations that lead to a decision. It would be great if we could hashtag that with #record or something for findability
-
Alexander
commented
We (enterprise users) really miss this feature. Being able to hashtag meeting, thread , announcement/ etc with #subject will dramatically simplify the usage and improve usability of Teams.
-
Anonymous
commented
Also strongly support hashtags being available. The more we use Teams the more important it is to be able to categorise content to find it easily later.
-
Anonymous
commented
Strongly support the addition of this feature. Would be very valuable addition...
-
Steven Tuttle
commented
Just like the absence of chronological-sort-ordering in a Teams channel, I am likewise stunned that Teams does not provide #some-hashtag aggregation functionality by default. A shockingly absent feature. Please jump on this issue.
-
Vijayaragavan
commented
Any update on this feature?
-
Anonymous
commented
Any update?
-
Pistle Jumbo
commented
Teams does not support hashtags, at least not yet, in a way Twitter or Yammer uses them. You can add them to discussions, OneNotes or inside documents too (if you so wish to – but usually just include the document in Teams discussion and use hashtag in there)
-
Anonymous
commented
If it aint a Zoom killer, it aint a priority.
-
Ngai Zhang
commented
Any update?
-
Jan
commented
Client looking at other tools than Teams now due to #hashtag feature missing, vital for this client to have it available across teams/channels/chats (where you have access). Would appreciate an update on this - backlog or being worked on or coming this fall... - Regards, Jan
-
Julian Carrasquillo
commented
very much interested in this functionality. we've got a tips and tricks channel and the ability to categorize items as 'python', 'spark', 'linux' would be great.
-
Jay
commented
We're using a channel in teams to share Development within the team, and would love the ability to categorise each little "nugget of wisdom" so that if someone wants to look up "Communication Development" they can just see posts related to that, rather than having to scroll through the whole thread. We had multiple channels for each category however that just resulted in too much noise, which Teams was brought in to reduce.
-
Anonymous
commented
This needs to be done if Teams is to be our primary repository.