raphael-batte

possible directions: 1. more clear visual 2. more clear messages/errors 3. option to see configuration details by new button.

Hypothesis. What if we move "remove@ button inside configuration? 

Thanks for the feedback! The idea looks interesting, we will discuss it in the UX team.

Possible directions from first explorations: 1. add more clear bot setup description to the OnCall documentation 2. add the TELEGRAM_TOKEN field setup to the Telegram settings tab (table will be...

UPD 1. add more clear setup steps description to the OnCall documentation 2. make more clear separation between org/personal Telegram 3. add description about 'localhost' limitations

If the user uses a hobby setup and his address is 'localhost', Telegram can't connect to OnCall. Solution is to make redirect by TELEGRAM_WEBHOOK_HOST more clear as step.

Proposal upd to the docs page https://grafana.com/docs/oncall/latest/open-source/#update-grafana-oncall-oss: 1. Ensure your OnCall environment is up and running. 2. Create OnCall bot via BotFather and request a key. Then add your key...

ChatOps setup upd: 

**Documentation:** **I. Setup connection to Telegram API** 1. Ensure your OnCall environment is up and running. 2. Create OnCall bot via BotFather and save HTTP API token which provided. 3....

Initial info for users. **ChatOps:** You can manage incidents directly in your team channel. Make sure your team connects Telegram in their OnCall user profiles too. Users can perform actions...