-
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
[Security Solution]'Export Selected' button is enabled for Pre-built elastic Rules #104582
Comments
Pinging @elastic/security-solution (Team: SecuritySolution) |
@manishgupta-qasource Please review!! |
Reviewed & assigned to @MadameSheema |
Pinging @elastic/security-detections-response (Team:Detections and Resp) |
@peluja1012 @spong please note that this question is listed on elastic/security-team#1412 ticket, can we confirm if this is a bug or an expected behaviour? Thanks ping @MikePaquette |
@spong @MadameSheema This is expected behavior as discussed in the original PR here. When users use the "select all" feature, we don't have an easy way to determine if "all" of the selected rules are prebuilt. However, when users select the current page or select individual rules, the "export" option should still be disabled appropriately for prebuilt rules. |
Hi @madamsheema, Thanks for the update!! We are considering this as expected behavior as mentioned in the comments!! |
Description:
'Export Selected' button is enabled for Pre-built elastic Rules
Build Details:
Version: 7.14.0 BC1
Commit: 071a74e
Build: 42292
Artifact Page : https://staging.elastic.co/7.14.0-8eba2f5f/summary-7.14.0.html
Browser Details:
All
Preconditions:
Steps to Reproduce:
Actual Result:
'Export Selected' button is enabled for Pre-built elastic Rules.
Success message "Successfully exported 0 of 553 rules. Prebuilt rules were excluded from the resulting file." is getting displayed by clicking on 'Export Selected' button.
Screen-Cast
Expected Result:
'Export Selected' button should be disabled for Pre-built elastic Rules.
What's not working:
What's working:
The text was updated successfully, but these errors were encountered: