GitHub Copilot for Jira Gets Smarter — MCP, Model Selection & Confluence Context
GitHub's latest Copilot update brings meaningful workflow improvements for teams already living in Jira and Confluence. The headline additions include model selection directly from within Jira — so developers can choose which underlying AI model handles a given task without leaving their project management context — and Jira ticket references surfaced directly inside pull requests, closing a long-standing gap between issue tracking and code review. Confluence context via MCP rounds out the update, letting Copilot pull in relevant documentation automatically when processing complex tickets.
Separately, OpenAI synchronized settings between the Codex desktop app and the VS Code extension, adding a convenient settings entry point accessible from within the extension itself. It's a small change, but it speaks to a deliberate push toward tighter IDE integration — and it's the kind of quality-of-life improvement that enterprise developers notice. When context and configuration carry seamlessly across tools, the cognitive overhead of switching between environments drops significantly.
Together, these updates reinforce a broader trend: AI coding tools are moving past the "impressive demo" phase and into deep workflow integration. The teams building the best developer tools right now aren't just optimizing for what's technically possible — they're optimizing for where developers already spend their time.