Joe

My feedback

  1. 6,933 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    While this might not seem like a huge priority, it is a viable short term alternative to the very important problem of organizing communication for teams with lots of projects, and would allow a team to manage multiple threads for multiple projects in a single channel (attaching communication by hashtag instead). There are a pile of OSS libraries for hashtag autocomplete on Github, is this really moving heaven and earth to get this implemented?

    Joe supported this idea  · 
  2. 938 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    188 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    partially done  ·  Warren responded

    As mentioned in the prior status, the channel limit was raised from 100 to 200.

    In the near future a retention limit will be set so you can still go back and reinstate a channel you had deleted. Once the retention period has expired then the channel will get a hard delete which will free up the space and no longer count toward the 200 channel limit.

    This will help with some of the issues you have voiced in the comments below.
    But I understand many of you wish the limit to be further increased. I will continue to provide your votes and comments to the feature team.

    -Warren

    An error occurred while saving the comment
    Joe commented  · 

    This is a huge limitation for your biggest paying customers. There are many business use cases where having a channel per project is necessary and now we are stuck merging multiple projects into the same channel (we have around 300 active projects per region at any given time, so this limit needs to be raised by an order of magnitude, not by a factor of 2 or whatever). This is going to become enough of a problem to consider pulling our business subscription and moving to a Slack/Google stack.

    Joe supported this idea  · 
  3. 1,347 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    196 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Joe supported this idea  · 
  4. 19,623 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1065 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Joe supported this idea  · 
  5. 32,051 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3997 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Joe supported this idea  · 

Feedback and Knowledge Base