<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Why does the Notable Incident Review Status dropdown have &amp;quot;No Matches&amp;quot;? in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-does-the-Notable-Incident-Review-Status-dropdown-have-quot/m-p/610140#M10992</link>
    <description>&lt;P&gt;We are in SplunkCloud with ES 7.0.0&lt;/P&gt;
&lt;P&gt;As a user with the sc_admin or ess_admin role when selecting an incident to edit, the drop-down for "Status" gives no matches. All other drop-downs give options as expected.&lt;BR /&gt;&lt;BR /&gt;We've tried enable/disable all statuses, creating new statuses, adding/removing transitions roles for ALL statuses, granting permissions to edit_reviewstatus for additional roles, granting write permissions to kvstore reviewstatuses_lookup, and several other things.&lt;/P&gt;
&lt;P&gt;Is there a key thing we are missing to be able to change status on incidents with the ess_admin user?&lt;/P&gt;</description>
    <pubDate>Fri, 19 Aug 2022 16:58:03 GMT</pubDate>
    <dc:creator>cjacklum</dc:creator>
    <dc:date>2022-08-19T16:58:03Z</dc:date>
    <item>
      <title>Why does the Notable Incident Review Status dropdown have "No Matches"?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-does-the-Notable-Incident-Review-Status-dropdown-have-quot/m-p/610140#M10992</link>
      <description>&lt;P&gt;We are in SplunkCloud with ES 7.0.0&lt;/P&gt;
&lt;P&gt;As a user with the sc_admin or ess_admin role when selecting an incident to edit, the drop-down for "Status" gives no matches. All other drop-downs give options as expected.&lt;BR /&gt;&lt;BR /&gt;We've tried enable/disable all statuses, creating new statuses, adding/removing transitions roles for ALL statuses, granting permissions to edit_reviewstatus for additional roles, granting write permissions to kvstore reviewstatuses_lookup, and several other things.&lt;/P&gt;
&lt;P&gt;Is there a key thing we are missing to be able to change status on incidents with the ess_admin user?&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2022 16:58:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-does-the-Notable-Incident-Review-Status-dropdown-have-quot/m-p/610140#M10992</guid>
      <dc:creator>cjacklum</dc:creator>
      <dc:date>2022-08-19T16:58:03Z</dc:date>
    </item>
    <item>
      <title>Re: Why does the Notable Incident Review Status dropdown have "No Matches"?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-does-the-Notable-Incident-Review-Status-dropdown-have-quot/m-p/612111#M11018</link>
      <description>&lt;P&gt;This turned out to be the sharing permissions on Enterprise Security App was set to "App".&lt;BR /&gt;The fix was to change this to "Global".&lt;/P&gt;</description>
      <pubDate>Tue, 06 Sep 2022 14:53:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/Why-does-the-Notable-Incident-Review-Status-dropdown-have-quot/m-p/612111#M11018</guid>
      <dc:creator>cjacklum</dc:creator>
      <dc:date>2022-09-06T14:53:03Z</dc:date>
    </item>
  </channel>
</rss>

