<?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/efac70e4a8d7433c9f9a6ee640c90e92&quot; frameborder=&quot;0&quot; width=&quot;2130&quot; height=&quot;1597&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1597</height><width>2130</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1597</thumbnail_height><thumbnail_width>2130</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/efac70e4a8d7433c9f9a6ee640c90e92-48486922b5432eb4.gif</thumbnail_url><duration>585.113</duration><title>Setting up JPD for Cross-Team Requests</title><description>In this video I show you how to reproduce the configuration for a central team requests system. I set up three spaces, platform team, product team, and team requests, then create two types called requests and solutions with global fields for request stage, source team, target team, and health. Next I create global connection fields for requests and solutions and add them to all three spaces so people can link work across teams. I also configure a required create form in the team requests space using a Request Form view filter on stage. Please make sure the team requests space visibility is open so anyone with a creator license can use it.</description></oembed>