[Security Solution]Dashboard not showing on import after tag auto generation

[ghost]

Describe the bug
Dashboard not showing on import after tag auto generation

Build Details:

Version:8.4.0 BC1
Commit:58f7eaf0f8dc3c43cbfcd393e587f155e97b3d0d
Build:54999

Steps

• Build fresh kibana
• Create a custom dashboard
• Go to Stack management> Tag
• Manage Security Solution tag and assign above custom dashboard
• now import the custom dashboard and then delete it
• now delete the Security Solution tag and generate a new one
• now import the dashboard back
• Observed that imported dashboard is not showing inside the security app as now we have two tag with same name but under tags we can see the attached SO

Screen-Cast

Tags.-.Elastic.Mozilla.Firefox.Private.Browsing.2022-08-03.15-11-28.mp4

[elasticmachine]

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

[elasticmachine]

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

[semd]

Not sure if this is a bug. The "problem" is that the original tag of the exported dashboard was deleted, when the dashboard is imported the original tag ID is not found so it is re-created, while there was another new tag with the same Security Solution name. Tags saved objects are not unique by name, so we end up with two Security Solution tags. This situation is rare but can happen under different circumstances.
The Dashboards landing page takes the first Security Solution tag it finds by creation date.
I will bring this to @paulewing.

[semd]

This PR is going to fix this bug by using all Security Solution tags to retrieve Security dashboards. #154174

[MadameSheema]

@karanbirsingh-qasource please validate the fix on current BC. Thanks.

[ghost]

Hi @MadameSheema

We have validated this issue on 8.8 BC2 and found the issue to be fixed ✔️ . Tag is not getting duplicate and dashboard import successfully.

Build Details:

Version: 8.8 BC2
Commit:33efd47ee6927b54b328e901fe31d31eae875325
Build:62857

Screen-Cast

part1_AdobeExpress.mp4

Hence we are Closing this issue and adding "QA:Source" tag to it.

thanks !!