video1.0<iframe src="https://www.loom.com/embed/cc329956f1e14d5595937beb33e1c8e6" frameborder="0" width="1280" height="960" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>9601280Loomhttps://www.loom.com9601280https://cdn.loom.com/sessions/thumbnails/cc329956f1e14d5595937beb33e1c8e6-bdd24a92f00b81aa.gif232.016Good morning everyone, my name is Shyam Sharma, and I'm excited to present my submission for Code Digest 2025: the Rovo Race Engineer. This tool draws parallels between Formula 1 racing and software releases, emphasizing that races—and releases—are often lost due to overlooked risks rather than speed. By analyzing Jira data, Rovo identifies the top three race-critical risks for a release, providing actionable insights to help teams prioritize effectively. I've shared the architecture and key components of the project, including the index.js file and manifest.yml, which connect the app to Jira. I encourage you to review the architecture diagram and consider how Rovo can enhance our release strategies.