From issue label to merged PR
cyql now picks up Linear and Jira issues automatically and closes the loop back to the ticket. Your issue tracker becomes the interface.
By The cyql team
The issue tracker is where most engineering work is defined. A ticket has a title, a description, an acceptance criterion, maybe a priority label. Everything cyql needs to plan and execute a task is already there — the friction was the manual step of copying it into a run.
With Linear and Jira triggers, that step disappears. Apply a label — the one your team designates for autonomous work — and cyql picks up the issue, reads the description, and starts a run. When the PR opens, it links back to the originating ticket and updates the issue status.
This matters for how teams think about their backlog. Issues that were too small to prioritize but too important to delete become viable again. You label them, cyql handles them, and the backlog shrinks without anyone spending sprint capacity on it.
The trigger label is configurable per project. You can use the same label across all repos or set different ones per team. Runs triggered from issues behave identically to manually started runs — they go through the same plan approval step if you have it enabled, produce the same traces, and respect the same guardrails.