<?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/24aec844c6a648679da3cc81c87505d3&quot; frameborder=&quot;0&quot; width=&quot;1512&quot; height=&quot;1134&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1134</height><width>1512</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1134</thumbnail_height><thumbnail_width>1512</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/24aec844c6a648679da3cc81c87505d3-4a73560e6e107a90.gif</thumbnail_url><duration>3333.784</duration><title>Using the External System Import</title><description>In this video, I explain how Ketryx issue types work in Jira projects. I highlight the importance of not using the default issue type scheme and how Ketryx handles issue types at different hierarchy levels. I also discuss the implications of syncing issue types with Ketryx and the impact on existing types. Viewers are advised on how to manage issue types effectively to avoid conflicts and maintain workflow integrity.</description></oembed>