Download topic as PDF
Fixed issues for Splunk Mission Control
Splunk Mission Control updates continuously. The following issues were recently fixed in Splunk Mission Control.
Splunk Mission Control
Date resolved | Issue number | Description |
---|---|---|
2024-03-28 | BLUERIDGE-7347 | Splunk SOAR repo roles fail to be created. |
2024-01-31 | BLUERIDGE-7378 | Session storage limit exceeded causing Investigations page to crash |
2024-01-09 | BLUERIDGE-6979 | Current implementation of display_id was resulting in skipping of display_id allocation in a few cases |
2024-01-04 | BLUERIDGE-7137, BLUERIDGE-7014 | The execution of mod input send ES field updates to Mission Control failed |
2024-01-03 | BLUERIDGE-7273 | When searching for a response template to add, the first time you select the response template search result the table entry is not selected. The Submit button also appears when there are no response template selections. |
2023-12-21 | BLUERIDGE-7194, BLUERIDGE-7285 | Notables ingested from Splunk Enterprise Security that were manually created have infomintime/infomaxtime that have no value |
2023-12-11 | BLUERIDGE-7014, BLUERIDGE-7137 | An existing incident can't be opened again after upgrading to Splunk Mission Control 3.0.1 |
2023-12-08 | BLUERIDGE-7184 | After upgrading Splunk Enterprise Security to 7.3 and editing the correlation search, the risk event timeline doesn't show up in Splunk Mission Control |
2023-12-07 | BLUERIDGE-7154 | Unicode and unescaped characters are used in the drilldown_searches for an incident |
2023-12-05 | BLUERIDGE-7126 | Notes added through Splunk SOAR with special characters crash page |
2023-11-30 | BLUERIDGE-5343 | Drop-down list options for filters in the incident review table are not scrollable |
2023-11-30 | BLUERIDGE-7129 | Drilldown searches in Incident Review aren't escaping characters |
2023-11-22 | BLUERIDGE-7055 | Risk Event Timeline unable to show data when the events consist of two or more events with 0 risk score. |
2023-11-22 | BLUERIDGE-6753 | Manually running a playbook containing a prompt from a response template doesn't update notification count unless the page is refreshed |
2023-11-16 | BLUERIDGE-6177, MCHELP-200 | Some users see a notification message similar to the following: User 'admin' triggered the '_reload' action on app 'missioncontrol', and the following objects required a restart |
Last modified on 29 March, 2024
PREVIOUS What's new in Splunk Mission Control |
NEXT Known issues for Splunk Mission Control |
This documentation applies to the following versions of Splunk® Mission Control: Current
Feedback submitted, thanks!