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] Text is getting misalligned for alert added comment on case on upgrading case from 7.11.1 --> 7.12.0 BC3 #93568

Closed
ghost opened this issue Mar 4, 2021 · 13 comments
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:critical This issue should be addressed immediately due to a critical level of impact on the 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 Mar 4, 2021

Describe the bug
Text is getting misalligned for alert added comment on case on upgrading case from 7.11.1 --> 7.12.0 BC3

Build Details:
Version: 7.12.0 BC3
Platform: Production
Commit:08417cbd6c15e4c866651a7dcdfeded58845206d
Build:39134

Browser Details
All

Preconditions
1.Elastic Cloud environment having version 7.12.0 should be available.
2.Auditbeat should be installed on above environment.
3.Detection Alert should be available on 7.11.1.
3.Jira and ServiceNow connector should be available.

Steps to Reproduce

  1. Navigate to Kibana and go to Security App from left navigation panel.
  2. Click on Detection Tab.
  3. Attach Detection Alert to "Create new Case".
  4. Upgrade the cloud instance to 7.12.0 BC3
  5. Observed that after update below mentioned text get misaligned.
    image

Actual Result
Text is getting misaligned for alert added comment on case on upgrading case from 7.11.1 --> 7.12.0 BC3

Expected Result
Text should not got misaligned after upgrade as it was displaying correctly on 7.11.1 and got broke on 7.12.0
image

Whats Working

  • N/A

Whats Not Working

  • N/A

Screenshots
image
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 Mar 4, 2021
@elasticmachine
Copy link
Contributor

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

@ghost ghost added the impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. label Mar 4, 2021
@ghost
Copy link
Author

ghost commented Mar 4, 2021

@manishgupta-qasource Please review

@manishgupta-qasource
Copy link

Reviewed & Assigned to @MadameSheema

@MadameSheema MadameSheema added the Team:Threat Hunting Security Solution Threat Hunting Team label Mar 4, 2021
@elasticmachine
Copy link
Contributor

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

@MadameSheema
Copy link
Member

@karanbirsingh-qasource can you please check if you are able to see the details of the alert clicking on the arrow? Thanks 😊

@ghost
Copy link
Author

ghost commented Mar 4, 2021

@karanbirsingh-qasource can you please check if you are able to see the details of the alert clicking on the arrow? Thanks 😊

Yes , we are do able to see more details of added alert by clicking on ">" arrow icon against the comment.

image

@ghost
Copy link
Author

ghost commented Mar 4, 2021

Additionally one thing more observation on this issue.

  • on 7.11.1
    Comment : Elastic added an alert from Malware detection alert
    image

  • After upgrading to 7.12.0

    • Malware detection rule name got changed to Unknown rule. 🔴
      image

@MadameSheema MadameSheema added impact:critical This issue should be addressed immediately due to a critical level of impact on the product. and removed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Mar 4, 2021
@MadameSheema MadameSheema removed their assignment Mar 4, 2021
@MadameSheema
Copy link
Member

Labeled as critical after a conversation with @MikePaquette

@MadameSheema
Copy link
Member

Found during 7.12.0 BC3 testing

@MadameSheema
Copy link
Member

@karanbirsingh-qasource can you please validate the fix of this issue on 7.12 BC4? Thanks :)

@ghost
Copy link
Author

ghost commented Mar 10, 2021

thanks for the update of issue fix on BC4 , we will validate this as soon as BC4 build got available on Cloud .

@ghost
Copy link
Author

ghost commented Mar 15, 2021

Hi @MadameSheema

we have validated this issue on 7.12.0 BC4 and found it Fixed . Case with Alert created on 7.11.1 , migrated correctly and detection alert comment entry reflects correctly.

Build Details:

Version: 7.12.0 BC4
Commit:99ac38d70e426f589bb61a034c96e602d759cfab
Build:39242

Snap-Shoot:
image
image

hence we are closing this issue.

thanks !!

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

ghost commented Mar 30, 2021

Bug Conversion:

Created 01 Test Case for ticket:
https://elastic.testrail.io/index.php?/cases/view/76937

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:critical This issue should be addressed immediately due to a critical level of impact on the 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

No branches or pull requests

3 participants