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

[Security Solution][Cases]No warning Triangle Icon for depreciated shown under Connector list while adding connector as Rule Action Item #114097

Closed
ghost opened this issue Oct 6, 2021 · 5 comments · Fixed by #115287
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Cases Cases feature impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@ghost
Copy link

ghost commented Oct 6, 2021

Describe the bug
No warning Triangle Icon for depreciated shown under Connector list while adding connector as Rule Action Item

Build Details

Version: 8.0.0
Build:9007199254740991

Precondition

  • Create connector on old kibana build let say 7.15.0 and upgrade it to 7.16.0

Steps

  • Login to upgrade kibana build
  • Go to any Rule and edit it and go to Rule Action setting
  • Click on ITSM or SecOps
  • Observed that No Triangle warning icon is showing for the Deprecated connector

Actual
No warning Triangle Icon for depreciated shown under Connector list while adding connector as Rule Action Item

Expected
Warning Triangle Icon for depreciated is should show under Connector list while adding connector as Rule Action Item

Ticket AC
image

Snap Shoot
image
image
image

logs

  • N/A
@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Oct 6, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-threat-hunting-cases (Team:Threat Hunting:Cases)

@ghost ghost added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Oct 6, 2021
@manishgupta-qasource
Copy link

Reviewed & assigned to @cnasikas

@MadameSheema MadameSheema added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. and removed triage_needed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Oct 6, 2021
@MadameSheema MadameSheema assigned semd and unassigned cnasikas Oct 6, 2021
@semd semd assigned jonathan-buttner and unassigned semd Oct 19, 2021
@cnasikas cnasikas added Feature:Cases Cases feature Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting:Cases labels Jan 10, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops-cases (Feature:Cases)

@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Cases Cases feature impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants