-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Actions] ServiceNow implement support for adding custom incident fields. #78237
Comments
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Moving from |
Pinging @elastic/response-ops-cases (Feature:Cases) |
Pinging @elastic/response-ops (Team:ResponseOps) |
Just adding a comment to let you know this is something we would really like to have :D |
I am closing the issue as it is already done. |
I am reopening the issue as I mistakenly assumed that it is resolved. Sorry for the inconvenience. |
Closing as it was implemented by #184023. We added an |
Currently we have only hardcoded default list of ServiceNow incident fields in alert action UI.
Maybe it could be implemented similar way as we have for Jira action params, by requesting the list of ServiceNow incident fields mapping.
The text was updated successfully, but these errors were encountered: