Ever wished you could go from a documentation page to a working pull request without manually connecting all the dots?
We have AI coding tools that can write code, documentation scattered across Confluence and repositories, and Jira to track our work. But turning a requirement into well-defined tickets, giving a coding agent the right context, running tests, and tracking the changes still involves a lot of manual effort.
What if we could connect these steps into one pipeline - one that takes us from documentation to Jira tickets to tested code, without being locked into a single AI coding tool?
In this session, we'll explore how to build that workflow using MCP, Jira, and a common interface for different coding agents. We'll look at what the architecture could look like, how to keep humans in control, and how to make the pipeline reusable across tools like Claude Code, Tabnine, and others.
And it’s not all learning! We’ll wrap up with a fun quiz based on the session, with exciting rewards for the winners. 🎁
The goal? Less time connecting the dots, more time building things that matter! See you there
Tesco
Software Development Engineer
Optimizory Technologies
Software Engineer