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] Updated name of external Connector is not reflecting on update button at case #92607

Closed
ghost opened this issue Feb 24, 2021 · 10 comments · Fixed by #93018
Closed
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team v7.12.0

Comments

@ghost
Copy link

ghost commented Feb 24, 2021

Describe the bug
Updated name of external Connector is not reflecting on update button at case

Build Details:

Platform : Production
Version : 7.12.0 BC2
Commit : 4f65a5a1268fa78f1af9117d12312e1cee433376
Build: 39000

Browser Details
All

Preconditions
1.Elastic Cloud environment having version 7.12.0 should be available.
2.Audit beat should be installed on above environment.
3.IBM Connector should be created on above environment.

let say connector name would be "ksingh_ibm_resilient connector"
image

Steps to Reproduce

  1. Navigate to Kibana and Select Security Solution App from the left navigation panel.
  2. Go to Case tab and add above IBM connector to it.
  3. Go to Edit External Connector again and update the existing name of IBM connector.
    let sat "ksingh_ibm_resilient connector updated"
    image
  4. Again go to created case.
  5. Observed that name of connector was not updated to current updated name.

image

Actual Result
Updated name of external Connector is not reflecting on update button at case

Expected Result
Updated name of external Connector should reflect on update button at case

Whats Working

  • N/A

Whats Not Working

  • N/A

Screenshots
image

logs
N/A

@ghost ghost added bug Fixes for quality problems that affect the customer experience Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Feb 24, 2021
@elasticmachine
Copy link
Contributor

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

@ghost
Copy link
Author

ghost commented Feb 24, 2021

@manishgupta-qasource Please review

@manishgupta-qasource
Copy link

Reviewed & assigned to @MadameSheema

@manishgupta-qasource manishgupta-qasource added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Feb 24, 2021
@MadameSheema MadameSheema added the Team:Threat Hunting Security Solution Threat Hunting Team label Feb 25, 2021
@elasticmachine
Copy link
Contributor

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

@MadameSheema MadameSheema removed their assignment Feb 25, 2021
@MadameSheema
Copy link
Member

@cnasikas @XavierM can you please take a look at this? Thanks :)

@MadameSheema
Copy link
Member

Bug found during BC2 regression: https://github.com/elastic/security-team/issues/843

@MadameSheema
Copy link
Member

@karanbirsingh-qasource can you please validate this on BC3? Lots of thanks :)

@ghost
Copy link
Author

ghost commented Mar 2, 2021

@karanbirsingh-qasource can you please validate this on BC3? Lots of thanks :)

sure @MadameSheema we will keep track of BC3 Availability and regress the same .

@ghost
Copy link
Author

ghost commented Mar 3, 2021

Hi @MadameSheema

we have validated this issue on 7.12.0 BC3 and found that issue is Fixed 🟢 . Now Updated name of connector is reflected there on Case .

Build Details:

Version: 7.12.0 BC3 
Platform: ON-PREM
Commit:08417cbd6c15e4c866651a7dcdfeded58845206d
Build:39134

Snap-Shoot:

  • Before Connector name updation
    image
  • After Connector name updation
    image

Hence we are Closing this Issue.

thanks !!

@ghost ghost closed this as completed Mar 3, 2021
@ghost ghost added the QA:Validated Issue has been validated by QA label Mar 3, 2021
@ghost
Copy link

ghost commented Mar 30, 2021

Bug Conversion:

Created 01 Test-Case for this Ticket
https://elastic.testrail.io/index.php?/cases/view/76932

Thanks!!

This issue was closed.
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 fixed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Threat Hunting Security Solution Threat Hunting Team v7.12.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants