You can use Power Automate to create an ADO work item (bug, user story, etc) when a user posts into specific Teams channel.
Log into Power Automate and create a new workflow. Find a Teams trigger that suits your need – in my case, I wanted to use a key word (you could even use different key words to create work items in different projects or with different content). Note that automation cycles accrue based on execution — so if you elect to link up to a busy Teams channel and filter for keywords to indicate you want an ADO item created, you may be “wasting” workflow cycles. In our case, I have a “user group” Teams space and set up a special channel where users can submit bug and feature requests. This means workflow cycles are accrued when someone specifically wishes to create an ADO item not when messages are posted into the user group’s general chat channels.
You can source messages from channels or group chats in the “Message type” selection. You cannot use hash-tags as key words! The workflow execution reports a gateway error. Select the Team and channel(s) that you want the workflow to monitor.
Add a new step to “create a work item” from Azure DevOps
Configure the project into which you want to create the work item – the organization and project name, the type of work item, and content of the work item.
If you want to set priority, add an assignment, etc – click on “Show advanced options”. I added a few fields to provide a clue as to where the bug report came from.
Save the workflow and post a message in your channel with the key word. Go into the ADO project work items; your Teams-initiated bug should be there.
I’ll admit it — I send myself emails. And text messages. And, back before smart phones, I sent myself voice messages too. That was one item where Teams was as step backwards — I had to make my own Teams space (with just me as a member!) in order to send myself notes here. But not anymore …
You can finally chat with yourself! Note that retention policies may be shorter in chats than Teams spaces … so you might still want to go the route of creating your own Teams space to ensure that note you send yourself for an end-of-the-year task or a list of accomplishments for your annual review are still around when you need them. But for quick notes so you remember something tomorrow (or next week, or three weeks from now), chatting with yourself is perfect for holding short-term reminders.
You ever navigate away from a discussion and realize you needed to go back — or not quite remember where you just posted that message? Teams now has a “Back” button — in the upper left-hand corner of the Teams client, you can click back and forth to navigate between the last 12 channels/chats you’ve visited.
Teams now shows the timezone offset and local time for individuals — because it’s always 2AM somewhere!
The contact card that comes up when you click on a user in Microsoft Teams now includes the current local time and time zone offset information for the individual — very useful to avoid ringing someone up at 2AM.
You can pin messages … but I wouldn’t say pinning a message has the result I’d expect. First, how to do it. On any channel message, you can click the ellipsis to access a menu. Select “Pin”.
You’ll get a warning that the message will be pinned for everyone … sounds good, right? If you want everyone to read the rules of the Teams space or to read the “NDA Applies To These Discussions” notice, you want the message pinned for everyone. Click “Pin” to continue.
Aaaand … everyone sees the message highlighted (and a little pin icon). The message is not, however, pinned to the bottom of the conversation list where everyone is sure to notice it. It is not displayed at the top of the current page where everyone is sure to notice it.
But there is a way to quickly view pinned messages in a channel. In the upper right-hand corner of the channel’s conversation list, find the little info icon. It’s the one you’ve never noticed because it didn’t do anything too useful … right next to the ‘meet’ button. Click it.
Scroll past the ‘About’ and ‘Members’ section of the info, and you will see any pinned posts.
If you start a chat with yourself from Outlook (or a group chat with a fake account you can then delete), you can get a “Just me” chat to send yourself messages. That’s not just me, right? You text yourself the three things you need to pick up at Home Depot too …
“Pinned” channels are basically links to channels that get a listing at the top of your Teams list for quick access. The way they list the pinned teams is kind of backwards in my mind — the big text is the channel name and the small text is the team name. So I’ve got a channel named “IT Maintenance and Outage Notifications” in the “NBI/NDI” team.
If you don’t want them pinned to the top, hover your mouse over the listing and an ellipsis will appear to open more options.
Click on ‘unpin’, and the pinned link to the channel will go away.
Can’t say I’ve needed to get an Outlook attachment into Teams myself – I try to store my files in OneDrive and e-mail links instead of e-mailing a copy of the file. When I need to update something, there’s no need to send an updated copy; and no one needs to figure out if they’re looking at the “right” version. Click the link now, and you have the right version. But there are certainly scenarios where you’d have attachments to share in Teams – especially if you interact with people outside of the organization. And you used to have to save the attachment and then share it into Teams. Not anymore – you can now drag attachments directly from Outlook into Teams (this works with the Teams web client too – but you cannot use the Outlook web client for this method. The message with an attachment needs to be opened in Outlook).
If you’ve got multiple monitors, this is easier … but, if not, shrink the Outlook window so you can see both the message and Teams. Then drag the attachment icon into the message composition box in Teams. You’ll see text that says “Drop your files here” appear in Teams.
Release the mouse, and the file will be uploaded to Teams.
Two new features announced that might be of interest to developers — the first one might provide a mechanism to move (well, copy) content between Teams spaces. You can read channel messages from a Teams space, analyze it, then use this new API to mirror the content into a new Teams space.
Two ways to add text to Microsoft Whiteboard sessions — ways that aren’t dragging your finger or mouse around in an attempt to draw legible text — are available. I’d like to be able to change the font in the text box — I get that their font choice is meant to evoke hand-written text, but it strikes me as non-professional.