Skip to main content
You have a bug filed as PROJ-123. Instead of copying the ticket into a prompt, you name it. The agent reads the ticket and its comments, names the task after it, writes a failing test, fixes the bug, and Bellows opens a pull request once your gates pass.

​
Before you start

  • The repository is set up with gates. See Configure a repository and Gates.
  • You can sign in to the Atlassian account that sees the ticket. The Jira connection is yours alone. See Connections.
  • The ticket says how to reproduce the bug and what should happen instead.

​
Steps

1

Connect Jira

Go to Settings → Integrations, then Browse integrations, and choose Jira. Click Connect, optionally fill Jira site (optional) with acme.atlassian.net, then click Continue to Atlassian and approve.Leave Allow adding comments off if the agent should only read tickets. Turn it on if you want it to be able to comment.
2

Create the task

Click New task, pick the repository (acme/notes-api) and an executor. Mention the ticket and the outcome you expect:
Prompt
Press Start task or ⌘ + Enter. Typing / opens the Skills menu. See Skills.
3

Connect on demand, if asked

If you have not connected Jira, the task page shows a block saying the task needs a Jira connection. Choose one:
  • Connect Jira, which opens the flow from step 1.
  • Use selected connection, if you have several. Pick the one for this task.
  • Continue without it, and the agent works without the ticket and says which Jira steps it skipped.
The task waits until you choose. After you connect, it resumes in the same session.
4

Watch the run

The task goes Queued, then Running. The agent reads the ticket, reading the comments too, since clarifications often land there. It then sets the task title from the ticket’s subject, for example “Fix 500 on notes with no title”. If you set a title yourself, the agent leaves it.It writes the failing test, fixes the code and runs the gates from .bellows.yaml. See Task lifecycle.
5

Review the pull request

When the gates pass, Bellows publishes the pull request and the task shows Waiting for review. Review it on GitHub. To change something, use Follow up on the task. Mark done closes the task in Bellows only; it does not merge the PR.

​
What you get

  • A pull request on acme/notes-api with a test that failed before the fix and passes now.
  • A task named after the ticket’s subject, so the inbox is easy to scan.
  • The gate results on the run, so you can see what was verified.

​
What the agent can and cannot do in Jira

If you turn on comments after a task started with read-only access, that task is refused. Start it again.

​
Tips

  • Put the reproduction steps and the expected behaviour in the ticket. The agent turns them into the failing test.
  • Add clarifications as ticket comments. The agent reads them.
  • Name the package or file in your prompt when you know it. See Writing good tasks.
  • For a subtask, mention it by key. The agent also reads the parent, where the real requirement usually lives.
  • Keep one ticket per task. A second ticket is a second PR.
  • If Jira answers “not found”, check that the connection’s site and your account can see the ticket. The agent stops and reports instead of guessing.

​
Variations

  • Ask the agent to comment the PR link on the ticket, with Allow adding comments on.
  • Skip /factory-fix for a change that is not a bug. Name the ticket and describe the work.