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

Webhook Input Field in Escalation Policy not Opening When Slack is Disabled #3263

Closed
mastercactapus opened this issue Sep 6, 2023 · 0 comments · Fixed by #3264
Closed

Webhook Input Field in Escalation Policy not Opening When Slack is Disabled #3263

mastercactapus opened this issue Sep 6, 2023 · 0 comments · Fixed by #3264
Labels
bug Something isn't working

Comments

@mastercactapus
Copy link
Member

Describe the Bug:
When trying to add a webhook on the Edit Step dialog in the Escalation Policy while Slack is disabled, the input field is not displayed at all and fails to expand as expected. This issue seems to be persistent across all browsers.

Steps to Reproduce:

  1. Go to the 'Edit Step' dialog in the 'Escalation Policy'
  2. Click on 'Add Webhook' while Slack is disabled
  3. Observe that the input field does not display or expand to allow user input.

Expected Behavior:
Upon clicking 'Add Webhook', the input field should expand to allow user to input data even when Slack is disabled.

Observed Behavior:
The input field does not display or expand when 'Add Webhook' is clicked with Slack disabled.

Application Version:
GoAlert version output:

Version:   v0.31.0-45-g0cd7d3265
GitCommit: 0cd7d326507399c5a3ccbb1d7082e23ce7e41c34 (clean)
BuildDate: 2023-09-06T09:37:15-05:00
GoVersion: go1.21.0 (gc)
Platform:  linux/amd64
Migration: alert-feedback-id (#237)

Additional Context:
This issue was found while trying to reproduce a user-reported bug. It appears to affect all browsers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant