Sean Burke

My feedback

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

    We’ll send you updates on this idea

    213 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Burke supported this idea  · 
  2. 15,405 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1321 comments  ·  Public » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.

    Sean Burke supported this idea  · 
  3. 18,934 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1262 comments  ·  Public » Calendar  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Burke supported this idea  · 
  4. 32 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    Agree with this, for another context. We have a regulatory requirement to set retention for the Chat tab to one day (a capability that is supposed to arrive at the end of this month). The challenge with Chat retention is that the files individuals are collaborating around in Chat also disappear if a chat goes stagnant and hits the retention limit. Right now this is less of an issue for our pilot users, since retention is at 30 days, but once we drop to one day, it will grow into a significant issue, rendering the value of file collaboration in chat limited.

    Sean Burke supported this idea  · 
  5. 2,856 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    392 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Sean Burke commented  · 

    I definitely DON'T want this idea. In our organization, we have compliance requirements that drive different retention policies across the Chat and Teams section. Keeping them separate makes it possible to delineate these areas clearly for our colleagues.

  6. 24,102 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2930 comments  ·  Public » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Burke supported this idea  · 
  7. 17,677 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1644 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
    Sean Burke supported this idea  · 

Feedback and Knowledge Base