{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/96e206ad8dea4aee9d2c5ea69d9fe5c3\" frameborder=\"0\" width=\"1280\" height=\"960\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":960,"width":1280,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":960,"thumbnail_width":1280,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/96e206ad8dea4aee9d2c5ea69d9fe5c3-7673f7bf89ed2fb3.gif","duration":300.168,"title":"Jira Coding Agent Workflow Demo, Simple vs High Risk","description":"I built a Jira coding agent demo that watches for new Jira ticket creation and autonomously makes code changes in a React repo. For a simple ticket, I cloned the repo, did RAG indexing, captured before and after screenshots, ran tests, and successfully created a PR showing updates in app.js and app.test.js. Then I created a high risk ticket, and the agent classified it as higher risk, presented a plan for review, and only after approval it implemented stateful click counter logic and created the PR. No action was requested from viewers in this Loom."}