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.

Sign up for GitHub

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

Jump to bottom

[ACTIONS] [CONNECTORs] Allow dynamic parameters for the connector #58780

Closed
XavierM opened this issue Feb 27, 2020 · 5 comments
Closed

[ACTIONS] [CONNECTORs] Allow dynamic parameters for the connector #58780

XavierM opened this issue Feb 27, 2020 · 5 comments
Labels
discuss estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@XavierM
Copy link
Contributor

XavierM commented Feb 27, 2020

Describe the feature:
For connectors like service-now, we would like to create dynamically parameters. So we can tell the service-now connector, how to map our data from our case to service-now.

Also to simplify everything, it might be nice if the connectors are just a proxy, so we can access and ask service-now what we want.

Describe a specific use case for the feature:
it is possible that users of service-now, we would like to map our case's fields to certain fields in service now.
@XavierM XavierM added Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Feb 27, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@pmuellr
Copy link
Member

pmuellr commented Feb 28, 2020

Could you provide a simple example? I think I know what you're talking about, but it would be useful to have a concrete example to work through.

@mikecote mikecote mentioned this issue Jun 17, 2020
Closed
@mikecote
Copy link
Contributor

Moved to discuss to gather more requirements.

@gmmorris gmmorris added Feature:Actions/Framework Issues related to the Actions Framework NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases labels Jul 1, 2021
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@ymao1
Copy link
Contributor

ymao1 commented Jul 29, 2021

@XavierM Is this issue still a relevant requirement?

@gmmorris gmmorris added the estimate:needs-research Estimated as too large and requires research to break down into workable issues label Aug 18, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@mikecote
Copy link
Contributor

Closing due to lack of activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discuss estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions NeededFor:Security Solution SIEM, Endpoint, Timeline, Analyzer, Cases Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@pmuellr @XavierM @gmmorris @kobelb @mikecote @ymao1 @elasticmachine