Due to prioritization of other work-items this has been moved to the backlog. We will update when it is being actively worked on again.
Howdy Suphatra, we really need this ability. Given that Teams was a beta when we started using it, a lot of conversation history has built up that we don't want to loose. Having used it for awhile now, we realize we would have setup things differently from the start. For example, we have a bunch of micro teams serving in a larger team - so we setup each with it's own group. But now we would like to move the different group channels under one group. If we can't merge channels for now, fine. But we should at least be able to move a channel from one group to another. Even if we had a power shell command for admins to override any warnings, that would be helpful. Is the issue related to a database primary key column? If this really isn't going to be possible, tell us now so we can decide if we should cut our losses and delete the channel, or wait a bit longer for a fix.
Also - when we first started using teams, we were still learning the best way to organize it. However we've learned a lot since the launch, and reorganizing the channels is a must!
Please add this feature soon! Because of organizational changes, we would like to move several channels to a team so we don't lose the history.
Clippy is flattered by all the attention but plans to continue his retirement.
This item is still under review. I’ll keep following up with the feature team and sharing all your feedback.
I’m switching the status to Partially Done.
The request for a Preview Team is still in the works. No new information is available at this time.
Team Discoverability is still being worked upon, no details are available at this time. If you support this idea please navigate over to the main topic and vote for it! https://microsoftteams.uservoice.com/forums/555103/
Change Prompt: this has been completed
This feature request has been declined.
Currently if you have the Teams app set to run in the background upon clicking the “X” in the upper right, the app stays active only in the system tray. If you receive chat messages, it still remains in the SysTray.
However, if you get an @mention, the focus pulls it to the Taskbar. This is by design since you are getting directly mentioned and some action is typically expected. This is a key design element which the team does not wish to deviate from.
We appreciate the suggestion but will respectively decline it at this time.
Thank you for the feedback and suggestion.
This is currently in internal testing rings at Microsoft, and the feature team is targeting a release to the public in early Q2.
~Alex & the Teams team
687 votes79 comments · Public » Apps, Connectors, Messaging Extensions · Flag idea as inappropriate… · Admin →
This request is still under review.
This request is still queued within our backlog. No new details yet.
I apologize, there had been come miscommunication with regards to this topic.
The good news is that this item has not been declined! It has actually been approved by the feature team and is now “On the Backlog”.
I’ll keep this thread updated as we move through the development.
So happy to share that this is off the backlog and we are actively working on it!
Due to a priority shift this request has slipped to the backlog. I hate to bring bad news. I will continue to provide the feature team your feedback and votes.
Hopefully this will move back up in the queue soon.
Thanks for following our suggestion to vote this up on SharePoint. It worked! SharePoint has confirmed that they have already started working on this and I’ll be getting an ETA from them after the holidays. -Suphatra
We are getting closer… the team is almost ready to rollout MacOS notification support internally for testing – we hope to have it to the public by the end of this quarter.