Owen Scott

My feedback

  1. 13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Owen Scott commented  · 

    This seems like a specific incident of the more general issue: Teams' on-the-fly Markdown parsing is really, really broken. Microsoft - could you please fix that, by stopping with automated parsing and leaving Markdown syntax in place, and then watch this entire long-tail of bugs melt away?

    Owen Scott supported this idea  · 
  2. 542 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    89 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  Suphatra responded

    We’re fixing bugs identified in the comments, and other user reports we’ve received around markdown, but we’ve decided we’re not going to fundamentally change our markdown support.

    This is the first time we’ve declined a request, and it didn’t come easily. We weighed this against other important features we’re working on to deliver and we had to make some tough choices.

    Really appreciate your understanding on this, and please feel free to ping me if you have any questions, complaints, or need to rant.

    Suphatra

    Owen Scott commented  · 

    I'm a Teams power-user, from one of the first large companies to use Teams. I still can't believe this has been marked as "won't fix" - to the point that I just come back to this thread routinely to post.

    The auto-parsing of Markdown (and the associated elimination of the formatting syntax) ruins all of the things that Markdown is good for, and makes using Teams into an incredibly frustrating experience. This is not what anyone wanted when they asked for Markdown support :(

    Please note the years of frustrated comments from otherwise happy users and re-open this issue.

    Owen Scott commented  · 

    Can you please fix this feature? It's a daily source of pain. You've tried to do some clever inline stuff but no one asked for that :(. Can we not just type in markdown and have it render on send???

    Owen Scott supported this idea  · 
    Owen Scott commented  · 

    Hi. Just a question: if you've been fixing bugs since August 3, why as of November have we not see fixes? The Markdown implementation in Teams is *completely* broken.

    Try typing the following and tell me that this is a product that Microsoft should have in the field:

    > The first variable is named `var1` and the second variable is named `var2`

    In examples like this you get an inline code span for "var1" (most of the time) but never for "var2". Please fix! Personally I don't want to see any new features added to Teams before this basic issue is solved... Fix bugs before shipping new features!

    Owen Scott commented  · 

    Adam's comment is spot on.

    `foo` and `bar` only highlights the first

    I also fine that once you create an autoformatted code block (e.g. using ```) it's impossible to uncreate it. This is a total dumpster fire and really should never have been shipped, especially to paying customers :(

    Could you please please please:

    1) Stop deleting formatting marks (e.g. "`", "*", etc.) during autoformatting. Just apply the formatting but leave the marks. Or don't auto-preview.
    2) Fix the parser

    This is our ability to collaborate on code.

  3. 55 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Owen Scott commented  · 

    Markdown support on teams has to move away from on-the-fly parsing. The approach has SO many problems. Please move to in-line formatting but leave the Markdown syntax itself in place...

    Owen Scott supported this idea  · 
  4. 237 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    35 comments  ·  Public » Meetings  ·  Flag idea as inappropriate…  ·  Admin →

    The OWA team has added a “Teams meeting” toggle in the new meeting item, as a preview feature. If you’d like to try it out, please turn on ""the new Outlook" toggle in the upper right corner. We’ll set this to completed once it’s fully released by the OWA team.

    Thanks!

    Owen Scott commented  · 

    Just to emphasize, this is getting unbearable. We have a lot of mixed remove/on-prem meetings, and we do everything on Teams; as a result 100% of meeting invites need a first-class Teams meeting embedded in them. However, the Teams calendar view doesn't support a bunch of important things, like inviting mailing lists, or room resources.

    PLEASE just add a checkbox that says "create Teams meeting" to the OWA meeting creation form.

    Owen Scott supported this idea  · 
  5. 12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Owen Scott commented  · 

    Microsoft, what is happening here?!? You've had a completely broken product in the field for months, and there are like a half-dozen user voice posts about it. This isn't a request for improvement - you've literally shipped something that doesn't work.

    Try typing the following and tell me that I'm wrong:

    > The first variable is named `var1` and the second variable is named `var2`

    In examples like this you get an inline code span for "var1" (most of the time) but never for "var2". Please fix! I don't want to see any new features added to Teams before this basic issue is solved...

    Owen Scott supported this idea  · 
  6. 67 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Owen Scott commented  · 

    Please please please fix the buggy (non) Markdown support and do it properly! Right now it's worse than not having it at all...

    Owen Scott supported this idea  · 

Feedback and Knowledge Base



You are about to visit the UserVoice site for Microsoft Teams

We have partnered with UserVoice, a 3rd party service providing public discussion forums for product-specific feedback.

By clicking "Continue to UserVoice" you agree to UserVoice's Privacy Policy and Terms of Use.