{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/024dddc50f8647d4b7856fbbd9f78e63\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/024dddc50f8647d4b7856fbbd9f78e63-8de0e1d8b037be13.gif","duration":96.988,"title":"Automating Jira to PR Workflow in Slack","description":"I kicked off a Resolve Jira flow from Slack and the agent immediately acknowledged it and started the workflow. It cloned the repo, created a branch, identified the fitting connector, in this case Databricks, ran analysis, then implemented the change, while streaming detailed updates to me. After implementation it ran evals, generated a SQL artifact, and then pinged me with a link to the PR and a Confluence summary page with acceptance criteria and notes. No action was explicitly requested from viewers, even though evals can fail and still provide useful follow ups."}