Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Respond to not-configured channels by default #876

Open
pkosiec opened this issue Dec 2, 2022 · 0 comments
Open

Respond to not-configured channels by default #876

pkosiec opened this issue Dec 2, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@pkosiec
Copy link
Collaborator

pkosiec commented Dec 2, 2022

Overview

After a conversation on the community Slack with Ben Mathews (link) and further investigation of the reported issue on a call, we found out that the issue consisted of a few factors, including a counter-intuitive default Botkube behavior.

Acceptance Criteria

Bring the following improvements:

  • Add an option (on by default) to respond to any channel. It could be turned off for multi-cluster scenarios
  • The default values.yaml only shows the "default" channel. Provide some additional (commented out) examples to demonstrate how a user might want to configure other channels
  • command move guard → too many info logs and warnings → move them to debug
  • Update docs

Reason

Improve user experience for new users.

@pkosiec pkosiec added the enhancement New feature or request label Dec 2, 2022
@pkosiec pkosiec added this to Botkube Dec 2, 2022
@mszostok mszostok added this to the v0.18.0 milestone Dec 15, 2022
@mszostok mszostok moved this to Todo in Botkube Dec 15, 2022
@pkosiec pkosiec removed this from the v0.18.0 milestone Jan 10, 2023
@pkosiec pkosiec removed the status in Botkube Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants