[Security Solution]Rebranding required in the Import modal text

[ghost]

Describe the bug
Rebranding required in the Import modal text

Build Details

Version: 7.16.0-SNAPSHOT
Commit:f002f58fd6cd35f8ecf97f5e64d1f836d96c51e5

Steps

• Go to Rule page of Detect Group
• click on Import button
• Observe the text in the modal that is Select Security rules (as exported from the Detection Rules page) to import and in that old page name that is Detection Rule page 🔴 is mentioned , rebranded name of page should be there either Rule Page or Detect Rule Page

Actual
Old page names is mentioned in the Import Rule Modal Text

Expected
Rebranding required in the Import modal text

Screen-Shoot

• Old Page naming
  

logs

• N/A

[elasticmachine]

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

[manishgupta-qasource]

Reviewed & assigned to @MadameSheema

[MadameSheema]

@jethr0null can you please take a look to this and help the team with a copy? Thanks :)

[rylnd]

@jethr0null we're looking for copy to address both the outdated navigation reference here, and also potentially to make mention of the new actions import/export behavior exposed in #115243. I'll start with a suggestion:

Select rules and actions (as exported from the Security > Rules page) to import

[jethr0null]

Thanks @rylnd.

I do have a couple of questions. Does that copy reflect the steps that the team is adding to the documentation? Also, would the user need to import multiple files (one for rules and one for actions) based on the implementation we've chosen? If not, it might be confusing to call out actions explicitly in the copy.

[bilelmeddeb]

hello @karanbirsingh-qasource . where did you find the 7.16.0 version ?

[ghost]

hello @karanbirsingh-qasource . where did you find the 7.16.0 version ?

Hi @bilelmeddeb I had reported this issue on 7.16.0-SNASHOT available on Elastic QA Cloud Platform. However same issue can be found on 7.16.0 BC1.

Build Details:

Version:7.16.0 BC1
Commit:9231d806c9384df4026977ba7435a9302dc2d4ab
Build:45504

[jethr0null]

For 7.16, let's go with the suggested copy and we can open a subsequent issue if we want to add information about actions and exceptions import once all of that functionality has been released.

Select rules and actions (as exported from the Security > Rules page) to import

[banderror]

@karanbirsingh-qasource the issue has been addressed and backported to 7.16. Should be available in BC5. Thank you.

[ghost]

Hi @banderror thanks for the comment.

we have validated this issue on 7.16.0 BC5 and found it fixed ✔️

Build Details:

version: 7.16.0 BC5
Commit:f13296db8798dd0cd39ab6cc4a61a35a2a2b05cc
Build:46061

Snap Shoot:

Hence we are closing this issue.

thanks !!

c.c @MadameSheema