Cuelight docs
Cuelight adds a Next steps panel to Jira work items. The panel shows buttons for the things
someone can do right now: send the work item to an AI agent, deploy to staging, run tests, promote
to production. A button either starts a GitHub Actions workflow or updates the work item in Jira.
Jira groups decide who can press it, and every press is recorded on the work item. It's a way to
trigger GitHub Actions from Jira without giving everyone GitHub access: each workflow button sends a
workflow_dispatch from Jira with the inputs you choose.
What makes the buttons change is the work itself. When a workflow finishes, one step in your YAML reports the result back and says which buttons should come next. Other tools, like a pull request workflow, n8n or an AI agent, can offer next steps too.
Start here
- Install on Jira: get the app on your Jira Cloud site in two minutes.
- Getting started: connect GitHub, add your first action and press it.
- Walkthrough: one ticket from To Do to Done, with every action and workflow file you need to copy.
- Concepts: actions, rules, runs, reports, next steps and offers.
Examples
- Workflow patterns: different steps on success and failure, progress messages, forms, branches per work item, multi-job workflows and Jira field updates.
- Recipes: complete setups for running an AI agent from Jira, agent pull requests, deploys, label automations and offers from any tool.
Reference
- Actions: every field of the action JSON.
- Rules and permissions: when a button shows and who can press it.
- Report API: hand back results and next steps from any tool.
- GitHub setup: token permissions and what a workflow needs.
When something goes wrong
- Troubleshooting: every error message, why it happens and how to fix it.
- FAQ: limits, data retention and how Cuelight fits next to Jira Automation.