Brouck

My feedback

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

    We’ll send you updates on this idea

    5 comments  ·  Public » Getting Started  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Warren responded

    This request is still under review by the feature team.

    -Warren

    Brouck supported this idea  · 
  2. 59 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 » Teams and Channels  ·  Flag idea as inappropriate…  ·  Admin →
    Brouck supported this idea  · 
  3. 230 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    on the backlog  ·  Warren responded

    This item is still on the backlog. I’ve received no further updates yet about this topic. I will continue to bring your feedback to the feature team.

    -Warren

    Brouck supported this idea  · 
  4. 1,178 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    218 comments  ·  Public » Bots  ·  Flag idea as inappropriate…  ·  Admin →
    Brouck supported this idea  · 
    An error occurred while saving the comment
    Brouck commented  · 

    Consider defining a "test" mode function, and making input and/or output while running in test mode being saved/archived with the capability of future retrieval and or deletion via a testing admin function. This would give us the ability to reproduce issues, save the output, delete the output from the normal displayed flow, and create documentation and/or submit support requests if the issue is part of the release codebase. Issues of testing vs. operational owner permissions could then be left up to the local discretion.

Feedback and Knowledge Base