From Jira

Not switched on yet. The flow on this page is built, but the Jira trigger is not enabled in the current deployment, so asks made in Jira will not be picked up right now. Use Slack, the dashboard, or GitHub in the meantime. Everything below describes how Jira will work once it's switched on.

After this page you can start a bee straight from a Jira ticket, either by moving it to the "AI" status or by @mentioning the agent in a comment, and know what to expect back on the ticket.

Path 1: move the ticket to "AI"

Fill in the ticket's "Github Repo" custom field with the target repo (3sidedcube/project-name or a full GitHub URL), then move the ticket to the "AI" status. That status transition is the trigger; other ticket edits are ignored. If the field is empty, the bee comments on the ticket asking you to add the repo and retry.

The ticket's summary and description become the task. By default the request goes to the swarm agent; add an exact bee-name label (support-bee, a11y-bee, tinfoil-bee, cleaner-bee) to run that recipe directly instead. Moving the same ticket to "AI" several times in quick succession folds into a single run, not several.

Path 2: comment on the ticket

The same webhook accepts issue comments, which do two different things:

• Start a run. A comment that @mentions the agent (a literal @cube-bees or @bee token) with no open conversation starts a fresh run, the same as a Slack mention. The bee acknowledges with an "on it, buzzing the Queen for this request" comment.
• Continue a run. If you started a run on this ticket and it is paused or open for follow-up, a plain comment from you (the original requester) continues the same run; no @mention needed. A comment from anyone else does not continue your run.

A plain comment with no open run and no @mention is ignored.

What the bee posts back

The bee narrates its lifecycle as ticket comments (the same updates also appear in a Slack thread in #cube-bees):

• Pickup: "Cube Bees: picked up this ticket for <repo>. Classifying the best recipe now." then "Cube Bees: Queen dispatched a worker for this ticket."
• Success: "Cube Bees: mission complete. PR opened: <PR URL>". The PR link lands as a comment on the ticket, and the ticket is transitioned to "Awaiting PR".
• Question or follow-up: the agent posts its question as a comment; reply on the ticket (or on the dashboard) to continue.
• Failure or no PR: an honest comment with the reason and verdict. The bee never goes silent.

Jira writes are soft-fail: a Jira outage never kills a run. The PR still opens and Slack still updates; only the ticket comments and status transitions go missing.

What makes a good ticket

The summary and description are the entire brief, so write them for a reader with no context:

• Name the repo in the "Github Repo" field; the bee cannot guess it.
• Concrete acceptance criteria in the description: "the /export endpoint returns CSV with these five columns", not "improve exports".
• One task per ticket. A ticket that bundles three changes gets one PR attempting all three.
• Point at specifics where you can: file paths, error messages, the failing test name.

Current limitations

• The trigger is not enabled in the current deployment (see the note at the top of this page). It shares the software@3sidedcube.com bot account with the legacy production fleet, and webhooks are JQL-scoped to test projects so the legacy fleet doesn't double-fire; check with the team before pointing it at a new project.
• Mentions must be the literal text @cube-bees or @bee. Picking the agent from Jira's @-mention account picker does not trigger a run yet.
• If your Jira profile hides your email address, your comments are ignored entirely: continuation is declined (the bee can't confirm you are the original requester) and a fresh @mention doesn't start a run either. Use the "AI" status transition instead, which still works with a hidden email.
• The target Jira workflow needs the "AI" and "Awaiting PR" statuses; if a transition isn't available the bee logs a warning and skips it rather than failing the run.