<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/c197c41b8fd54516b7eb3eb0305f29b0&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c197c41b8fd54516b7eb3eb0305f29b0-7456d7a799ac4c3b.gif</thumbnail_url><duration>110.017</duration><title>Syncing Glide Duration Fields Between ServiceNow and Jira</title><description>In this video, I walk through the process of syncing a dummy field called &apos;dd&apos; from ServiceNow to Jira, highlighting how I&apos;ve populated it with glide duration information. I explain that while the ticket was initially synced with blanks, I&apos;ve now filled in the raw value in Jira&apos;s remote number field. Additionally, I demonstrate how I&apos;ve manipulated the due date field to reflect a timestamp with an added duration, which should translate to a specific date in January. The key takeaway is that while the data appears as text, there&apos;s significant potential for manipulation. Please take a look at the custom field setup to see how I&apos;ve integrated these values.</description></oembed>