<?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>question Assignment Rule triggered when Incident Priority Updates.  in ITSM forum</title>
    <link>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546988#M118767</link>
    <description>&lt;P&gt;According to ServiceNow Docs, the Assignment Rules will only run when a Task record is unassigned. Let's say we have&amp;nbsp; a ticket that was manually re-assigned to a new &lt;STRONG&gt;Assignment Group&lt;/STRONG&gt;. What I am noticing in most cases, when this assigned ticket has either the &lt;STRONG&gt;Impact&lt;/STRONG&gt; or &lt;STRONG&gt;Urgency&lt;/STRONG&gt; updated,&amp;nbsp;this action appears to re-run the assignment rule. This also clears out the Incident&amp;nbsp;&lt;STRONG&gt;Assign to&lt;/STRONG&gt; field.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For unsuspecting ITIL users that then save the&amp;nbsp;Incident, this&amp;nbsp;results in the Assignment Group changing. How is it possible that the ticket is getting re-assigned? How do we prevent the tickets from re-assigning?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"The task record must be unassigned. The record cannot have an existing value for either the&amp;nbsp;&lt;SPAN class="keyword option"&gt;assigned_to&lt;/SPAN&gt;&amp;nbsp;or&amp;nbsp;&lt;SPAN class="keyword option"&gt;assignment_group&lt;/SPAN&gt;&amp;nbsp;fields. Assignment rules cannot overwrite existing assignments (including assignments set by a default value or a previously run assignment rule)."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.servicenow.com/bundle/madrid-platform-administration/page/administer/task-table/concept/c_AssignmentRulesModule.html" rel="nofollow"&gt;https://docs.servicenow.com/bundle/madrid-platform-administration/page/administer/task-table/concept/c_AssignmentRulesModule.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;JB&lt;/P&gt;</description>
    <pubDate>Fri, 02 Aug 2019 17:11:28 GMT</pubDate>
    <dc:creator>JahanzebB</dc:creator>
    <dc:date>2019-08-02T17:11:28Z</dc:date>
    <item>
      <title>Assignment Rule triggered when Incident Priority Updates.</title>
      <link>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546988#M118767</link>
      <description>&lt;P&gt;According to ServiceNow Docs, the Assignment Rules will only run when a Task record is unassigned. Let's say we have&amp;nbsp; a ticket that was manually re-assigned to a new &lt;STRONG&gt;Assignment Group&lt;/STRONG&gt;. What I am noticing in most cases, when this assigned ticket has either the &lt;STRONG&gt;Impact&lt;/STRONG&gt; or &lt;STRONG&gt;Urgency&lt;/STRONG&gt; updated,&amp;nbsp;this action appears to re-run the assignment rule. This also clears out the Incident&amp;nbsp;&lt;STRONG&gt;Assign to&lt;/STRONG&gt; field.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For unsuspecting ITIL users that then save the&amp;nbsp;Incident, this&amp;nbsp;results in the Assignment Group changing. How is it possible that the ticket is getting re-assigned? How do we prevent the tickets from re-assigning?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"The task record must be unassigned. The record cannot have an existing value for either the&amp;nbsp;&lt;SPAN class="keyword option"&gt;assigned_to&lt;/SPAN&gt;&amp;nbsp;or&amp;nbsp;&lt;SPAN class="keyword option"&gt;assignment_group&lt;/SPAN&gt;&amp;nbsp;fields. Assignment rules cannot overwrite existing assignments (including assignments set by a default value or a previously run assignment rule)."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.servicenow.com/bundle/madrid-platform-administration/page/administer/task-table/concept/c_AssignmentRulesModule.html" rel="nofollow"&gt;https://docs.servicenow.com/bundle/madrid-platform-administration/page/administer/task-table/concept/c_AssignmentRulesModule.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;JB&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 17:11:28 GMT</pubDate>
      <guid>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546988#M118767</guid>
      <dc:creator>JahanzebB</dc:creator>
      <dc:date>2019-08-02T17:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: Assignment Rule triggered when Incident Priority Updates.</title>
      <link>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546989#M118768</link>
      <description>&lt;P&gt;That sounds move like a Lookup Rule than an Assignment Rule. If you disable the Assignment rule does the issue not occur?&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 18:25:02 GMT</pubDate>
      <guid>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546989#M118768</guid>
      <dc:creator>Michael Fry1</dc:creator>
      <dc:date>2019-08-02T18:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: Assignment Rule triggered when Incident Priority Updates.</title>
      <link>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546990#M118769</link>
      <description>&lt;P&gt;There is a Data Lookup Rule, but all that does is set the Priority based on the Impact and Urgency. This particular Data Lookup rule does not update the assigned to or the assignment group with an impact or urgency change.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Assignment Rule in this case use the Incident &amp;gt; Applies to Condition &amp;gt; Priority 1 or 2 to set the Assignment Group. I did disable this particular assignment rule, but the Incident is still assigning when Priority is modified.&lt;/P&gt;
&lt;P&gt;Is there a way to troubleshoot and check which assignment rule ran or was taking precedence?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 20:57:31 GMT</pubDate>
      <guid>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546990#M118769</guid>
      <dc:creator>JahanzebB</dc:creator>
      <dc:date>2019-08-02T20:57:31Z</dc:date>
    </item>
    <item>
      <title>Re: Assignment Rule triggered when Incident Priority Updates.</title>
      <link>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546991#M118770</link>
      <description>&lt;P&gt;There is a Data Lookup Rule, but all that does is set the Priority based on the Impact and Urgency. This particular Data Lookup rule does not update the assigned to or the assignment group with an impact or urgency change.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Assignment Rule in this case use the Incident &amp;gt; Applies to Condition &amp;gt; Priority 1 or 2 to set the Assignment Group. I did disable this particular assignment rule, but the Incident is still assigning when Priority is modified.&lt;/P&gt;
&lt;P&gt;Is there a way to troubleshoot and check which assignment rule ran or was taking precedence?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Aug 2019 17:29:56 GMT</pubDate>
      <guid>https://www.servicenow.com/community/itsm-forum/assignment-rule-triggered-when-incident-priority-updates/m-p/546991#M118770</guid>
      <dc:creator>JahanzebB</dc:creator>
      <dc:date>2019-08-05T17:29:56Z</dc:date>
    </item>
  </channel>
</rss>

