<?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 Reopened Tickets still show under closed in My Requests for user in Developer forum</title>
    <link>https://www.servicenow.com/community/developer-forum/reopened-tickets-still-show-under-closed-in-my-requests-for-user/m-p/3508489#M1250674</link>
    <description>&lt;DIV&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;When a technician reopens an SCTASK, the associated REQ or RITM does not get updated. As a result, the request continues to appear under &lt;STRONG&gt;Closed Requests&lt;/STRONG&gt; when the user views it in &lt;STRONG&gt;My Requests&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Could you please suggest a solution for this issue and advise how we can fix it?&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 16 Mar 2026 09:16:04 GMT</pubDate>
    <dc:creator>BattuLakshmi</dc:creator>
    <dc:date>2026-03-16T09:16:04Z</dc:date>
    <item>
      <title>Reopened Tickets still show under closed in My Requests for user</title>
      <link>https://www.servicenow.com/community/developer-forum/reopened-tickets-still-show-under-closed-in-my-requests-for-user/m-p/3508489#M1250674</link>
      <description>&lt;DIV&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;When a technician reopens an SCTASK, the associated REQ or RITM does not get updated. As a result, the request continues to appear under &lt;STRONG&gt;Closed Requests&lt;/STRONG&gt; when the user views it in &lt;STRONG&gt;My Requests&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Could you please suggest a solution for this issue and advise how we can fix it?&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 16 Mar 2026 09:16:04 GMT</pubDate>
      <guid>https://www.servicenow.com/community/developer-forum/reopened-tickets-still-show-under-closed-in-my-requests-for-user/m-p/3508489#M1250674</guid>
      <dc:creator>BattuLakshmi</dc:creator>
      <dc:date>2026-03-16T09:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Reopened Tickets still show under closed in My Requests for user</title>
      <link>https://www.servicenow.com/community/developer-forum/reopened-tickets-still-show-under-closed-in-my-requests-for-user/m-p/3509853#M1250807</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/981162"&gt;@BattuLakshmi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;You can create a &lt;STRONG&gt;Flow Designer&lt;/STRONG&gt; flow that triggers when the &lt;STRONG&gt;State&lt;/STRONG&gt; of an &lt;STRONG&gt;SCTASK&lt;/STRONG&gt; changes from &lt;STRONG&gt;Closed&lt;/STRONG&gt; to &lt;STRONG&gt;Open&lt;/STRONG&gt;. The flow logic would be as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Get the related &lt;STRONG&gt;RITM&lt;/STRONG&gt;&lt;BR /&gt;↓&lt;/LI&gt;&lt;LI&gt;If the &lt;STRONG&gt;RITM&lt;/STRONG&gt; is in a &lt;STRONG&gt;Closed&lt;/STRONG&gt; state, reopen it&lt;BR /&gt;↓&lt;/LI&gt;&lt;LI&gt;Get the related &lt;STRONG&gt;REQ&lt;/STRONG&gt;&lt;BR /&gt;↓&lt;/LI&gt;&lt;LI&gt;If the &lt;STRONG&gt;REQ&lt;/STRONG&gt; is in a &lt;STRONG&gt;Closed&lt;/STRONG&gt; state, reopen it&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In addition, we should add a &lt;STRONG&gt;Wait for Condition&lt;/STRONG&gt; on the SCTASK until it is closed again. Once the SCTASK is closed, the flow can proceed to close the corresponding &lt;STRONG&gt;RITM&lt;/STRONG&gt; and &lt;STRONG&gt;REQ&lt;/STRONG&gt; as needed.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Huynh Loc&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Mar 2026 04:06:25 GMT</pubDate>
      <guid>https://www.servicenow.com/community/developer-forum/reopened-tickets-still-show-under-closed-in-my-requests-for-user/m-p/3509853#M1250807</guid>
      <dc:creator>Huynh Loc</dc:creator>
      <dc:date>2026-03-18T04:06:25Z</dc:date>
    </item>
  </channel>
</rss>

