<?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/168ac6ed961148268ffdbb60d4e122c5&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/168ac6ed961148268ffdbb60d4e122c5-985c03f1b480e451.gif</thumbnail_url><duration>900.257</duration><title>Atlassian System of Work Feature Request to Delivery</title><description>In this Loom, I walk you through Atlassian System of Work and how work moves end to end across Jira Service Management, Jira Product Discovery, Confluence, Jira, Bitbucket, and Loom. I start with a customer feature request in JSM, triage it in product discovery, brainstorm in Confluence, and create Jira stories from sticky notes. Development tracks and builds in Jira, manages code in Bitbucket, and QA tests and records steps to reproduce in Loom. When QA finds a bug, they create a Jira bug report with the Loom link. If you have questions, let me know.</description></oembed>