FAQ
How is this different from Jira Automation's manual trigger?
Jira Automation has no built-in action that starts a GitHub Actions workflow, so teams use a manual trigger with Send web request to the GitHub API (how to set it up). That starts the run, but the result stays in GitHub unless the workflow writes back to Jira, nothing offers the next step, and each run counts toward your Automation usage. Cuelight has a workflow action with a form, writes the result to the work item and lets the run offer what comes next.
The two work well together: a Cuelight button can add a label that an Automation rule already listens for. See Keep your label automations and the full comparison on Why Cuelight.
Do people need GitHub access?
No. Cuelight checks their Jira groups and starts the workflow with the token an admin saved.
Does Cuelight use AI or send my code to an AI?
No. Cuelight has no AI model and doesn't call one. When someone presses a button, it sends one
request to api.github.com that starts your workflow with the inputs you defined. If that workflow
runs an AI agent, the agent runs on your GitHub Actions runner with your own API key, and your
workflow decides what it sees. The work item fields you put in an action's inputs go to GitHub with
that request, and from there only where your workflow sends them.
Which agents work?
Any agent that runs in GitHub Actions, like Claude Code or OpenAI Codex. Cuelight starts the workflow and gets the result back, whatever runs in between. See Run Claude Code or Codex from Jira and Approve after an agent's pull request.
An agent that runs somewhere else can still offer a next step on a work item with one HTTPS request. See Offer a next step from any tool.
Which Jira does it work with?
Jira Cloud. Data Center isn't supported. Work items used to be called issues, so if you were looking for buttons in Jira issues, this is the same thing: the panel shows on every work item type.
Which CI systems does it support?
GitHub Actions for starting work. Anything that can send an HTTPS request can offer next steps, including other CI systems.
What does Cuelight store, and for how long?
Your action definitions, project mappings and run history, and each work item's current next steps. Everything is in Atlassian's Forge storage. Run history is kept for 180 days. Next steps expire after 7 days unless the report sets another time. See Security.
What leaves Atlassian?
Only the workflow dispatch sent to api.github.com: repository, workflow, ref, the inputs you
defined, the callback URL and the run token.
Can a workflow add any button it likes?
No. Reports and offers can only suggest actions an admin already defined, and Cuelight checks the presser's groups when the button is pressed.
What are the limits?
| Limit | Value |
|---|---|
| Actions | 100 |
| Form fields per action | 10 |
| Workflow inputs per action | 23, plus Cuelight's 2 |
| Next steps on a work item | 5 |
| Report body | 16 KB |
| Run token lifetime | 24 hours |
| Time before "No report received" | 30 minutes |
| Run history | 180 days, last 200 on the Runs tab |
Can I turn off the comments on work items?
Yes, per action, with "audit": { "comment": false }. The run history still records every press.
What happens to someone's name after they leave?
Cuelight follows Atlassian's personal data reporting. When an account is closed, its name in run history is replaced with "Former user".