<?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/1daadbf0ab334070bd5c5a2c94abc31d&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/1daadbf0ab334070bd5c5a2c94abc31d-94473968773a1517.gif</thumbnail_url><duration>258.271</duration><title>Atlassian UI Fixes and Lineage Bug</title><description>In this Loom I shared my open ended Atlassian contributions, one by one. First, I fixed a constrained object response that was not showing in the UI, and I added a test. Second, I fixed a CSS issue where table text turned white on selection. Third, I fixed a scrolling issue in large tables by using getBoundingClientRect in the React logic. Fourth, I fixed lineage not connecting when the case differed between Trello and database table names, adding tests and a PR to ensure both sides show. No action is specifically requested from you.</description></oembed>