Steve Elkind

My feedback

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

    We’ll send you updates on this idea

    42 comments  ·  Public » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind supported this idea  · 
  2. 1,537 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    228 comments  ·  Public » Guest Access  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind supported this idea  · 
  3. 26,610 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3251 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Steve Elkind commented  · 

    I just had a business development guy go and reorganize files and directories at the SharePoint level since the original channel structure chosen when creating the team is no longer scaling - and the people who were using Teams got flummoxed because all the files disappeared. I had to undo that.

    We will now have a discussion about whether to abandon Teams because of this inflexibility and inability to refactor. It's been almost two years since this was first requested, and many months since it was "put on the backlog". We can't wait around any longer

    Steve Elkind supported this idea  · 
    An error occurred while saving the comment
    Steve Elkind commented  · 

    Any news? We're starting to suffer from our original organization concepts for Teams, and we're very far down the road in some of the channels we'd like to split off into their own teams.

    An error occurred while saving the comment
    Steve Elkind commented  · 

    I'm sorry, but refactoring of teams and channels should have been designed in from the beginning. If you start out with a poor organization of them, then you're stuck with them. Being able to move channels around, or even better, promote channels into teams when it becomes obvious they need a larger scope. We have been unable to come up with a workaround. The ability to refactor would be an obvious need in the face of reorgs, agile projects, etc. would be something I would think to be an obvious feature.

    An error occurred while saving the comment
    Steve Elkind commented  · 

    Just came into situation where I needed to "promote" a channel into its own team. Being able to do this in some fashion would be a critical benefit to us. Having to create a new team, and then piece-by-piece trying to copy resources (conversations, ...) seems to be too time-intensive and much may not have good results. Even just moving the channel from the old team to a new one would be usable.

  4. 2,082 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    288 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind supported this idea  · 
  5. 167 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind supported this idea  · 
  6. 3,411 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    338 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    working on it  ·  Suphatra responded

    Hi everyone, the engineer working on this item has left the company and we’re working on replacing him. I wanted to give you that heads up because the work has paused, which extends our shipping date.

    I really appreciate your patience as we work to get this back to actively worked on.

    Suphatra

    Steve Elkind supported this idea  · 
  7. 1,745 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    267 comments  ·  Public » Desktop  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind supported this idea  · 
  8. 8 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 » Files  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Steve Elkind commented  · 

    Somebody showed me a roundabout way to sync to a local desktop by opening in SharePoint from Teams, then syncing from the SharePoint folder. The kicker is, it looks like it only works on a machine with O365-sourced Office 2016 installed. This isn't going to work for the laptop I normally use when working remotely, which has my personal copies of Visio and Project 2013 installed (and there's no O365 license for those where I'm working).

    Steve Elkind shared this idea  · 
  9. 18,665 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1694 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind supported this idea  · 
  10. 47 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind supported this idea  · 
  11. 58 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Public » Wiki  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Steve Elkind commented  · 

    I agree. i view Confluence as perhaps the best wiki I've ever used, and I usually get forced to a poor MS substitute with reasons such as "SharePoint is a wiki". In Teams there are only two levels of hierarchy, and no easy hyperlinking to result in a richer hierarchy. I hate to say it, but the Teams wiki is way too limited to be of much use.

  12. 71 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 » Planner  ·  Flag idea as inappropriate…  ·  Admin →
    Steve Elkind shared this idea  · 

Feedback and Knowledge Base