[Security Solution] [Bug] Time for the next run is not specified for the Bulk upload Asset criticality

[muskangulati-qasource]

Describe the bug
Time for the next run is not specified for the Bulk upload Asset criticality

Kibana/Elasticsearch Stack version

VERSION: 8.16.0
BUILD: 78245
COMMIT: b5dcc0db8dc72e25fcda6894ed6f24b6959b15b3

Steps

1. Kibana version 8.16.0 or above should exist
2. securitySolution:enableAssetCriticality flag should be enabled for Asset Criticality
3. Navigate to Security >> Manage >> Asset criticality
4. Create a file according to the example given
5. Click on ‘select or drag and drop a file’
6. Add the file created
7. Click on assign and observe for the output message:
   • The next scheduled engine run is in:
8. The time is not specified

Expected Result

• Time for the next run should be specified for the Bulk upload Asset criticality

Screenshot

[elasticmachine]

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

[muskangulati-qasource]

Hi @amolnater-qasource,

Please review!

[amolnater-qasource]

Reviewed & assigned to @MadameSheema

[elasticmachine]

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

[jaredburgettelastic]

👀 will address between 8.16 FF and release, tracking in EA's prioritized backlog here

[machadoum]

PR: #196496

[jaredburgettelastic]

@machadoum this was reopened, although the PR above was merged. Is there more work to be done on this one? Thanks!

[muskangulati-qasource]

Hi @jaredburgettelastic & @machadoum,

The ticket was reopened for the reason: It was pending for QA Validation.

We have validated this issue on 8.16.0 BC1 and found the issue to be fixed ✔️

Build Details:

VERSION: 8.16.0
BUILD: 79314
COMMIT: 5575428dd3aef69366cddb4ccf07a2a26d30ce48

Screenshot

Hence we are closing this issue and adding "QA:Validated" tag to it.

cc: @MadameSheema

Thanks!!