Jamie Thomson
My feedback
-
2 votesJamie Thomson
shared this idea
·
-
1 vote
-
2 votesJamie Thomson
commented
The idea, rightly or wrongly, is that you're supposed to use search to find your old conversations
-
6 votesJamie Thomson
supported this idea
·
-
28 votesJamie Thomson
commented
Glad to see this has made it onto the backlog.
Commenter Andrew has it spot on with " oblivious to how the web works"
Jamie Thomson
commented
Here is a gif demoing the problem https://t.co/alt276w5iL
Jamie Thomson
commented
update...just tried it on a colleague's Windows10 machine...same happens there
Jamie Thomson
shared this idea
·
-
1 voteJamie Thomson
commented
"Does not have landscape" == "totally immature"
Ok
-
28 votesJamie Thomson
commented
This request is basically a clone of https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32684689-combine-conversations. Please can you merge them together.
Jamie Thomson
commented
I came on here to as for exactly this, thank you to the person that already raised it.
This is definitely a problem - I often see people starting new conversations when they should be replying to existing ones. Its clearly an accident on their part but given it happens so often (and believe me, it does) I'm led to believe that the UI is somewhat to blame. Its not just novice users that do it either, I've seen extremely IT-literate people that are experienced in using Teams making the same mistake.
I find the problem occurs more often when people are replying via a phone app, the distinction there between replying to a new conversation starting a new one is less pronounced.
I think the ability to merge conversations together would be really useful. I suggest the following rules around it:
- 2 conversations can only be merged if they are in the same channel
- Conversation merging can only be done either by the person that started the conversation that is going to be merged, or by a team owner
-If the two conversations each have many messages then the resulting merged conversation might be even messier than when they were separate (due to messages from both conversations being mixed together). The person doing the merge should have the opportunity to preview what the merged conversation would look like.Jamie Thomson
supported this idea
·
-
30 votesJamie Thomson
commented
This request is basically a clone of https://microsoftteams.uservoice.com/forums/555103-public/suggestions/31822258-ability-to-move-a-conversation-inside-an-existing. Please can you merge them together.
-
28 votesJamie Thomson
commented
a gif to demonstrate why the current "Copy Link" (aka permalink) feature is so broken https://t.co/alt276w5iL
When I select "Copy Link" I expect to get a link (i.e. a URL) in my clipboard, not some rich text that is useless when pasted into a tool that doesn't recognise it.
Jamie Thomson
commented
A "Copy link" feature has appeared in teams at some point in the recent past. Unfortunately (as at 2018-04-09) it doesn't work. Reported here: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/33896725--copy-link-aka-permalink-doesn-t-work-properly
So so so bad.
Jamie Thomson
commented
Please read https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32866744-scenario-for-channel-chat-header-and-permalinks for a scenario where this would be useful
Jamie Thomson
commented
Another need for this arose today. I'm having a discussion on a pull request in a gitlab repo. There was a conversation in Teams a few weeks ago that pertains to the discussion being had in gitlab but there's no way of referencing that Teams conversation. All I need is URL (aka a permalink) to that conversation which I can include in the gitlab pull request.
Please...we need URLs (aka permalinks) for conversations and messages permalinks. URLs for deeplinking are the currency of the web, they make the web what it is...its so disappointing that Teams does not support them.
(gitlab is essentially an on-premises github)
Jamie Thomson
commented
If a message permalink is pasted into another message then I'd expect that message to get quoted or presented in a nice readable way, similar to how public links are today.
Jamie Thomson
commented
ignore my reference to the Teams desktop app, actually we need this from everywhere (i.e. all client apps, and the web app).
Whenever I see a message in Teams I'd like to be able to get a permalink to it.
Jamie Thomson
shared this idea
·
-
18 votes
-
3 votesJamie Thomson
commented
This happens for me also. I think (but can't be certain) that I only receive such notifications on my phone (with is an iOS device). In other words, in the desktop app I am not receiving notifications for Teams that I used to be a member of, but I *am* receiving those notifications in iOS.
This is a bug. Please fix.
Jamie Thomson
supported this idea
·
-
43 votes
This feature is now in the planning stages!
I hope to have more details to share soon.
-WarrenJamie Thomson
commented
Basically... copy whatsapp’s “share live location” feature.
Jamie Thomson
commented
I like this idea a lot. When I'm using the mobile app I want to share my location with my colleagues - would be invaluable for a mobile workforce. My iphone allows me to share my location with anyone I want and I use that to share my location with my family. I don't want to share my lcoation with my colleagues all the time though, so make it a feature of Microsoft Teams and allow me to specify which times of the day my location should be shared.
It might even be a way for a company to passively monitor the location and travel history of their workforce. Make it mandatory for members of a Team to share their location (or perhaps make it a condition of joining a Team). Of course, a company should only be able to monitor their employees' location during work hours, and this feature should reflect that.
I suspect there are loads of scenarios where this would be valuable. For example, a logistics company could know where all its delivery drivers are at any one time by plotting their locations in a Microsoft Teams tab.
Jamie Thomson
supported this idea
·
-
3 votesJamie Thomson
shared this idea
·
-
8 votesJamie Thomson
commented
Backtick bugs seem to have been fixed
They’ve stated elsewhere they’re not investing in improving markdown tho :( -
41 votesJamie Thomson
commented
2018-02-09 most of the problems mentioned here and in the comments now seem to have been fixed
Jamie Thomson
commented
I concur. I'm seeing this also
Jamie Thomson
supported this idea
·
-
6 votesJamie Thomson
shared this idea
·
-
1 voteJamie Thomson
shared this idea
·
-
178 votes
This feature request is still be reviewed by the feature team. No additional details are available at this time.
-Warren
Jamie Thomson
commented
Please read https://microsoftteams.uservoice.com/forums/555103-public/suggestions/32866744-scenario-for-channel-chat-header-and-permalinks for a scenario where this would be useful
Jamie Thomson
commented
How about combining with this: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18556948-editable-channel-header-using-markdown
In short, let us put markdown into the channel description
Jamie Thomson
shared this idea
·
-
3 votesJamie Thomson
shared this idea
·
-
672 votes
This item is still on the backlog.
No additional details to provide, but the team does understand this is a big need from the community.
I’m working on getting more information and possibly an ETA. I’ll keep you posted.
-Warren
Jamie Thomson
commented
Its a minor irritation but an irritation nonetheless. To me, 11/4 is the 11th April, not 4th November which teams seems to think it is. Please fix.
How about a constructive comment about how Teams could help?