In many cases, when I post a code snippet, it's an excerpt from a longer file. And usually, it's not starting at line 1 in that file.

While I very much appreciate that code snippets in Teams come with line numbers, it would be great if we could configure the first line number for a given snippet.

Like that, I could send a message such as: "Hey Jane, have a look at the following block from our file \BusinessLogic\Success\BestClass.cs: <snippet>". For the snippet, I'd set the starting line number to 42 because I've copied lines 42 to 51, and this would be immediately obvious from the snippet.

Bonus points for a way to insert "ellipses" (lines in the snippet that indicate something is skipped and that advance the line counter by a custom number of lines). Would make citing a couple of related lines spread throughout a long file a lot easier.

Your current Mac version available for download as of Jan 25 2019 installs an app with version 1.00.21761.

The previous version was apparently 1.00.131953

While 1.00.21 is a higher version than 1.00.13 unfortunately for any software that take into account the entire version string (like automated updaters/patching tools) version 1.00.131953 is a whole 110,192 versions *ahead* of 1.00.21761 :-/

This leads to scenarios where Teams may auto-update itself to x.21761 but automated patching sees that the version is now below the x.131953 version in our software repository and so re-installs that version. A fun loop.

Then when we add .21761 to the repository it won't install over top because the repo version is now *lower* than the existing installation of .131953 on the workstations.

Please ensure for future versions you can keep the numbering actually in the same decimal range...

PS - Our workaround is to trim our version checking to look at just the first 10 chars of the app's version string but really, if you're going to have a version number in the multi-100Ks, please just ensure it's consistently in that range for each release!

Dear Microsoft,

Feedback for the MS Teams application

We have reported 3 different issue still none of them fixed

1.When user creating a Teams account not able to get the SharePoint site to upload files

We have already reported this issue about 3 month back, still there is no solution for that one.
MS engineers are in a hurry to close all the times, not giving any solution yet (agreed one thing, MS engineer provided a workaround)

2. Teams status is not changing when locking the pc immediately

During the initial troubleshooting they suggested to check lot if things from the organization level
After sever days they conclude this case, saying it’s a default behavior

3. switching different Teams account keep the status of previous account in the same state for several days, until the user manually login back to the account

Similar to the above lot of troubleshooting done still no resolution

Same as above MS confirming it’s a default behavior

Please let me know when we get permanent solution for this, when i checked in the interest may article says it’s a competitor for Slack.
if you ask someone which is better MS Teams or slack(already using slack), definitely they go for slack only, because lot of bug in this MS Teams