Liam

My feedback

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

    We’ll send you updates on this idea

    910 comments  ·  Public » Wiki  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 
  2. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 
  3. 4 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 » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Liam commented  · 

    Agreed - the SharePoint list should be fully functional, with the ability to launch flows on its items.

    Liam supported this idea  · 
  4. 13,637 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    It would make a lot of sense for our organisation to have one channel per project. Sadly, the limit on number of channels rules that out. If we were able to archive channels (assuming they were then not counted towards the channel) we'd be able to do that, instead of having to place all conversations on active projects in one channel.

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

    We’ll send you updates on this idea

    45 comments  ·  Public » Mobile  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 
  6. 37 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Bug Reports » Files  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Liam commented  · 

    Same here, but with a folder. Once pinned via Teams, the folder shows as pinned in SharePoint, but the pin disappears from the Teams view upon reloading. Windows app, 1.3.00.4461 (64 bit).

    Liam supported this idea  · 
  7. 7,767 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    662 comments  ·  Public » Messaging  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Liam commented  · 

    This continues to be a major issue. It's simply too easy for a busy user to fire off a series of new conversations that were intended to be a replies to an existing one. There needs to be either a brake placed on this process - for instance requiring users to press a "New conversation" button to enable the text field - or there needs to be a way to retrospectively associate orphan messages with existing conversations.

    It's remarkable that this issue was flagged up nearly three years ago and still isn't fixed, despite it requiring relatively minor UI changes.

    Liam supported this idea  · 
  8. 8,644 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    756 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →

    if you have an existing post that you want to show in a different channel, you can edit the message and cross-post. This will add the top-level post to the different channel, but will not include the full set of replies. We will keep this request in mind as we evolve the cross-posting feature in the future and update if the status changes.

    Details on cross posting can be found here: https://support.office.com/article/cross-post-a-channel-conversation-in-teams-9c1252a3-67ef-498e-a7c1-dd7147b3d295.

    Liam supported this idea  · 
  9. 16,759 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1185 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 
  10. 4,282 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    on the backlog  ·  300 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 
  11. 21 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 » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 
  12. 24 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Public » Interoperability  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 
    An error occurred while saving the comment
    Liam commented  · 

    Same here - .docx files work, .doc files (of which we have many) do not. It's not an option to convert our legacy files to .docx as other software requires them to be .doc. If collaboration features are not possible then the best behaviour would be to fall back to a read-only view of the .doc.

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

    We’ll send you updates on this idea

    444 comments  ·  Public » Files  ·  Flag idea as inappropriate…  ·  Admin →
    Liam supported this idea  · 

Feedback and Knowledge Base